Local information disclosure via uninitialized swiotlb bounce buffer
Published Jul 16, 2024 · Updated May 11, 2026
Information disclosure in Linux 2.6.12 through 5.17 allows local users to read prior I/O data through a crafted SG_IO request. For a DMA_FROM_DEVICE mapping that the device does not overwrite, swiotlb copies stale bounce-buffer contents back instead of preserving the initialized input. Reachability requires access to an SG_IO device using swiotlb bounce buffering, as in a protected virtio-scsi guest; exposure is limited to residual I/O data.
Summary
What happened
Information disclosure in Linux 2.6.12 through 5.17 allows local users to read prior I/O data through a crafted SG_IO request. For a DMA_FROM_DEVICE mapping that the device does not overwrite, swiotlb copies stale bounce-buffer contents back instead of preserving the initialized input. Reachability requires access to an SG_IO device using swiotlb bounce buffering, as in a protected virtio-scsi guest; exposure is limited to residual I/O data.
The record
- CVE
- CVE-2022-48853
- Published
- Jul 16, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <06cb238b0f7ac1669cb06390704c61794724c191
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7007c894631cf43041dcfa0da7142bbaa7eb673c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <901c7280ca0d5e2b4a8929fbe0bfb007ac2a6544
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <aaf166f37eb6bb55d81c3e40a2a460c8875c8813
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b2f140a9f980806f572d672e1780acea66b9a25c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dcead36b19d999d687cd9c99b7f37520d9102b57
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f2141881b530738777c28bb51c62175895c8178b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f3f2247ac31cb71d1f05f56536df5946c6652f4a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd97de9c7b973f46a6103f4170c5efc7b8ef8797
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo