Kernel heap corruption via undersized UDF name buffer
Published May 1, 2025 · Updated Aug 5, 2026
Out-of-bounds write in the Linux kernel UDF filesystem allows local users to corrupt kernel heap memory through a crafted UDF image. udf_find_entry() allocates copy_name for a 254-byte UDF name, but memcpy can copy a 255-byte file identifier assembled across blocks, writing past the slab object. A local low-privileged user must mount the image and trigger a VFS lookup; successful exploitation can crash the host or corrupt kernel data.
Summary
What happened
Out-of-bounds write in the Linux kernel UDF filesystem allows local users to corrupt kernel heap memory through a crafted UDF image. udf_find_entry() allocates copy_name for a 254-byte UDF name, but memcpy can copy a 255-byte file identifier assembled across blocks, writing past the slab object. A local low-privileged user must mount the image and trigger a VFS lookup; successful exploitation can crash the host or corrupt kernel data.
The record
- CVE
- CVE-2022-49846
- Published
- May 1, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=066b9cded00b8e3212df74a417bb074f3f3a1fe0 <03f9582a6a2ebd25a440896475c968428c4b63e7
- Affected versionversion=066b9cded00b8e3212df74a417bb074f3f3a1fe0 <583fdd98d94acba1e7225e5cc29063aef0741030
- Affected versionversion=066b9cded00b8e3212df74a417bb074f3f3a1fe0 <7a6051d734f1ed0031e2216f9a538621235c11a4
- Affected versionversion=066b9cded00b8e3212df74a417bb074f3f3a1fe0 <ac79001b8e603226fab17240a79cb9ef679d3cd9
- Affected versionversion=066b9cded00b8e3212df74a417bb074f3f3a1fe0 <c736ed8541605e3a25075bb1cbf8f38cb3083238
- Affected versionversion=066b9cded00b8e3212df74a417bb074f3f3a1fe0 <c8af247de385ce49afabc3bf1cf4fd455c94bfe8
- Affected versionversion=066b9cded00b8e3212df74a417bb074f3f3a1fe0 <d8971f410739a864c537e0ac29344a7b6c450232
- Affected versionversion=066b9cded00b8e3212df74a417bb074f3f3a1fe0 <f1517721c408631f09d54c743aa70cb07fd3eebd
- Affected versionversion=4.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
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