Kernel data disclosure via uncleared report padding
Published Apr 24, 2026 · Updated Apr 24, 2026
Information disclosure in Linux Kernel allows local users to read three uninitialized kernel padding bytes through XFRM reports. In xfrm_user build_report(), the kernel sets individual xfrm_user_report members without first clearing the structure, then copies its three alignment-padding bytes to userspace. Exploitation requires local low-privileged access and the ability to request an XFRM report; the disclosed data is limited to three bytes per response.
Summary
What happened
Information disclosure in Linux Kernel allows local users to read three uninitialized kernel padding bytes through XFRM reports. In xfrm_user build_report(), the kernel sets individual xfrm_user_report members without first clearing the structure, then copies its three alignment-padding bytes to userspace. Exploitation requires local low-privileged access and the ability to request an XFRM report; the disclosed data is limited to three bytes per response.
The record
- CVE
- CVE-2026-31671
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 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 <0616314b3b34f24cbb91da8c6bd8bcdc4c8592f9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0a30dceb0e1f0c480d2482e6d7cebf8aebb6eb72
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6c55714c931051cd7f4839c19ce0867179fd22fe
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <716c546e88cfe49d841658240e10cb57bc50a2cc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d10119968d0e1f2b669604baf2a8b5fdb72fa6b4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d27c02eec529f78055a46a5c9e6c62684382b2d8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e0c8542c3d097ed4205ded51868195d5d6ddac62
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ff5ee507302303b15859753c3e0d67d38fd12c88
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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