Memory overwrite via header-inclusive payload zeroing
Published Oct 14, 2026 · Updated Oct 14, 2026
Out-of-bounds writing in Linux drop_monitor allows local users to exceed a Netlink alert buffer's requested payload by four bytes. The reset_per_cpu_data() function includes the attribute header in the length passed to memset() even though zeroing begins after that header. Starting monitoring requires administrative access; allocator padding complicates the reported corruption, and the retrieved sources demonstrate no crash or privilege escalation.
Summary
What happened
Out-of-bounds writing in Linux drop_monitor allows local users to exceed a Netlink alert buffer's requested payload by four bytes. The reset_per_cpu_data() function includes the attribute header in the length passed to memset() even though zeroing begins after that header. Starting monitoring requires administrative access; allocator padding complicates the reported corruption, and the retrieved sources demonstrate no crash or privilege escalation.
The record
- CVE
- CVE-2026-98419
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 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=2.6.31
- Affected versionversion=683703a26e4677db437a1480682851e27c7a154f <03b672eba4937ff18337049824a114012d57f202
- Affected versionversion=683703a26e4677db437a1480682851e27c7a154f <439f392084f8f7f59ab9d47a9579185accefe1d8
- Affected versionversion=683703a26e4677db437a1480682851e27c7a154f <530ae0a1458078c7a81fbffd9ff17d42129364d9
- Affected versionversion=683703a26e4677db437a1480682851e27c7a154f <56b12f0cd476e4d90a0e2663a80102b388ebf78c
- Affected versionversion=683703a26e4677db437a1480682851e27c7a154f <88d640efd655b10f9fa4e381caf777da1f17c2a6
- Affected versionversion=683703a26e4677db437a1480682851e27c7a154f <8a04047c6dbff2f49a561b1ff53b043f4807e855
- Affected versionversion=683703a26e4677db437a1480682851e27c7a154f <caf09c09e0f323015ab6777ed1bad5aa10688631
- Affected versionversion=683703a26e4677db437a1480682851e27c7a154f <d54a044136b129822715e8798899af540ec7a9e9
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started