Reinstate some of "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""
In the Linux kernel, the following vulnerability has been resolved: swiotlb: fix info leak with DMA_FROM_DEVICE The problem I'm addressing was discovered by the LTP test covering cve-2018-1000204. A short description of what happens follows: 1) The test case issues a command code 00 (TEST UNIT READY) via the SG_IO interface with: dxfer_len == 524288, dxdfer_dir == SG_DXFER_FROM_DEV and a corresponding dxferp. The peculiar thing about this is that TUR is not reading from the device. 2) In sg_start_req() the invocation of blk_rq_map_user() effectively bounces the user-space buffer. As if the device was to transfer into it. Since commit a45b599ad808 ("scsi: sg: allocate with __GFP_ZERO in sg_build_indirect()") we make sure this first bounce buffer is allocated with GFP_ZERO. 3) For the rest of the story we keep ignoring that we have a TUR, so the device won't touch the buffer we prepare as if the we had a DMA_FROM_DEVICE type of situation. My setup uses a virtio-scsi device and the buffer allocated by SG is mapped by the function virtqueue_add_split() which uses DMA_FROM_DEVICE for the "in" sgs (here scatter-gather and not scsi generics). This mapping involves bouncing via the swiotlb (we need swiotlb to do virtio in protected guest like s390 Secure Execution, or AMD SEV). 4) When the SCSI TUR is done, we first copy back the content of the second (that is swiotlb) bounce buffer (which most likely contains some previous IO data), to the first bounce buffer, which contains all zeros. Then we copy back the content of the first bounce buffer to the user-space buffer. 5) The test case detects that the buffer, which it zero-initialized, ain't all zeros and fails. One can argue that this is an swiotlb problem, because without swiotlb we leak all zeros, and the swiotlb should be transparent in a sense that it does not affect the outcome (if all other participants are well behaved). Copying the content of the original buffer into the swiotlb buffer is the only way I can think of to make swiotlb transparent in such scenarios. So let's do just that if in doubt, but allow the driver to tell us that the whole mapped buffer is going to be overwritten, in which case we can preserve the old behavior and avoid the performance impact of the extra bounce.
- Published
- Jul 16, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 17th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.9.320
- linux linux kernel4.10 and later · before 4.14.281
- linux linux kernel4.15 and later · before 4.19.245
- linux linux kernel4.20 and later · before 5.4.189
- linux linux kernel5.5 and later · before 5.10.110
- linux linux kernel5.11 and later · before 5.15.29
- linux linux kernel5.16 and later · before 5.16.15
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fd97de9c7b973f46a6103f4170c5efc7b8ef8797affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before aaf166f37eb6bb55d81c3e40a2a460c8875c8813affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 06cb238b0f7ac1669cb06390704c61794724c191affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b2f140a9f980806f572d672e1780acea66b9a25caffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before f3f2247ac31cb71d1f05f56536df5946c6652f4aaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7007c894631cf43041dcfa0da7142bbaa7eb673caffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before dcead36b19d999d687cd9c99b7f37520d9102b57affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before f2141881b530738777c28bb51c62175895c8178baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 901c7280ca0d5e2b4a8929fbe0bfb007ac2a6544affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.16.18-1 | 5.16.18-1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-default-base | before 5.3.18-150200.24.203.1.150200.9.105.1 | 5.3.18-150200.24.203.1.150200.9.105.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-docs | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-obs-build | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-preempt | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-source | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-syms | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-64kb | before 5.14.21-150400.24.194.1 | 5.14.21-150400.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-docs | before 5.14.21-150400.24.194.1 | 5.14.21-150400.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-obs-build | before 5.14.21-150400.24.194.1 | 5.14.21-150400.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-source | before 5.14.21-150400.24.194.1 | 5.14.21-150400.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-syms | before 5.14.21-150400.24.194.1 | 5.14.21-150400.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-64kb | before 5.14.21-150500.55.133.1 | 5.14.21-150500.55.133.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-docs | before 5.14.21-150500.55.133.1 | 5.14.21-150500.55.133.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-obs-build | before 5.14.21-150500.55.133.1 | 5.14.21-150500.55.133.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-syms | before 5.14.21-150500.55.133.1 | 5.14.21-150500.55.133.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.237.1 | 4.12.14-122.237.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_63 | before 1-8.3.1 | 1-8.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP2 | kernel-default | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise Live Patching 15 SP2 | kernel-livepatch-SLE15-SP2_Update_52 | before 1-150200.5.3.1 | 1-150200.5.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_48 | before 1-150400.9.7.1 | 1-150400.9.7.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_34 | before 1-150500.11.3.1 | 1-150500.11.3.1 |
| SUSE:Linux Enterprise Micro 5.2 | kernel-default | before 5.3.18-150300.59.232.1 | 5.3.18-150300.59.232.1 |
| SUSE:Linux Enterprise Micro 5.2 | kernel-default-base | before 5.3.18-150300.59.232.1.150300.18.138.1 | 5.3.18-150300.59.232.1.150300.18.138.1 |
+15
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 06cb238b0f7ac1669cb06390704c61794724c191 | Vendor (CNA) |
| Linux Linux | 7007c894631cf43041dcfa0da7142bbaa7eb673c | Vendor (CNA) |
| Linux Linux | 901c7280ca0d5e2b4a8929fbe0bfb007ac2a6544 | Vendor (CNA) |
| Linux Linux | aaf166f37eb6bb55d81c3e40a2a460c8875c8813 | Vendor (CNA) |
| Linux Linux | b2f140a9f980806f572d672e1780acea66b9a25c | Vendor (CNA) |
| Linux Linux | dcead36b19d999d687cd9c99b7f37520d9102b57 | Vendor (CNA) |
| Linux Linux | f2141881b530738777c28bb51c62175895c8178b | Vendor (CNA) |
| Linux Linux | f3f2247ac31cb71d1f05f56536df5946c6652f4a | Vendor (CNA) |
| Linux Linux | fd97de9c7b973f46a6103f4170c5efc7b8ef8797 | Vendor (CNA) |
| debian:linux | 5.16.18-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 5.3.18-150200.24.203.1 · SUSE:Linux Enterprise Live Patching 15 SP2 | Package registry (OSV) |
| suse:kernel-default-base | 5.3.18-150200.24.203.1.150200.9.105.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kernel-docs | 5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP2_Update_52 | 1-150200.5.3.1 · SUSE:Linux Enterprise Live Patching 15 SP2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_34 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kernel-preempt | 5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150500.13.118.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-source | 5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150500.13.118.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-syms | 5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_63 | 1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0977 · Jul 17, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/06cb238b0f7ac1669cb06390704c61794724c191
- git.kernel.org/stable/c/7007c894631cf43041dcfa0da7142bbaa7eb673c
- git.kernel.org/stable/c/901c7280ca0d5e2b4a8929fbe0bfb007ac2a6544
- git.kernel.org/stable/c/aaf166f37eb6bb55d81c3e40a2a460c8875c8813
- git.kernel.org/stable/c/b2f140a9f980806f572d672e1780acea66b9a25c
- git.kernel.org/stable/c/dcead36b19d999d687cd9c99b7f37520d9102b57
- git.kernel.org/stable/c/f2141881b530738777c28bb51c62175895c8178b
- git.kernel.org/stable/c/f3f2247ac31cb71d1f05f56536df5946c6652f4a
- git.kernel.org/stable/c/fd97de9c7b973f46a6103f4170c5efc7b8ef8797
- git.kernel.org/stable/c/270475d6d2410ec66e971bf181afe1958dad565e
- git.kernel.org/stable/c/6bfc5377a210dbda2a237f16d94d1bd4f1335026
- git.kernel.org/stable/c/7403f4118ab94be837ab9d770507537a8057bc63
- git.kernel.org/stable/c/8d9ac1b6665c73f23e963775f85d99679fd8e192
- git.kernel.org/stable/c/971e5dadffd02beba1063e7dd9c3a82de17cf534
- git.kernel.org/stable/c/c132f2ba716b5ee6b35f82226a6e5417d013d753
- git.kernel.org/stable/c/d4d975e7921079f877f828099bb8260af335508f
- git.kernel.org/stable/c/ddbd89deb7d32b1fbb879f48d68fda1a8ac58e8e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.