Upstream information
Description
TensorFlow is an end-to-end open source platform for machine learning. When a user does not supply arguments that determine a valid sparse tensor, `tf.raw_ops.SparseTensorSliceDataset` implementation can be made to dereference a null pointer. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either `indices` or `values` are provided for an empty sparse tensor when the other is not. If `indices` is empty, then [code that performs validation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference. If `indices` as provided by the user is empty, then `indices` in the C++ code above is backed by an empty `std::vector`, hence calling `indices->dim_size(0)` results in null pointer dereferencing (same as calling `std::vector::at()` on an empty vector). We have patched the issue in GitHub commit 02cc160e29d20631de3859c6653184e3f876b9d7. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having important severity.
| CVSS detail | National Vulnerability Database |
|---|---|
| Base Score | 2.1 |
| Vector | AV:L/AC:L/Au:N/C:N/I:N/A:P |
| Access Vector | Local |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | None |
| Availability Impact | Partial |
| CVSS detail | National Vulnerability Database |
|---|---|
| Base Score | 5.5 |
| Vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| Attack Vector | Local |
| Attack Complexity | Low |
| Privileges Required | Low |
| User Interaction | None |
| Scope | Unchanged |
| Confidentiality Impact | None |
| Integrity Impact | None |
| Availability Impact | High |
| CVSSv3 Version | 3.1 |
SUSE Security Advisories:
- openSUSE-SU-2022:10014-1, published Sat Jun 18 22:42:57 2022
List of released packages
| Product(s) | Fixed package version(s) | References |
|---|---|---|
| SUSE Package Hub 15 SP3 |
| Patchnames: openSUSE-2022-10014 |
| openSUSE Leap 15.3 |
| Patchnames: openSUSE-2022-10014 |
| openSUSE Tumbleweed |
| Patchnames: openSUSE-Tumbleweed-2024-12116 |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products past their end of life and not receiving proactive updates anymore. | ||
| SUSE Package Hub 15 SP3 | bazel-skylib1.0.3 | Released |
| SUSE Package Hub 15 SP3 | bazel3.7 | Released |
| SUSE Package Hub 15 SP3 | tensorflow2 | Released |
| SUSE Package Hub 15 SP3 | tensorflow2-lite | Released |
| SUSE Package Hub 15 SP3 | tensorflow2_2_6_0-gnu-hpc | Released |
| SUSE Package Hub 15 SP3 | tensorflow2_2_6_0-gnu-openmpi2-hpc | Released |
SUSE Timeline for this CVE
CVE page created: Mon Aug 16 09:53:32 2021CVE page last modified: Thu Dec 11 16:57:47 2025