Kernel memory corruption via stale ARP pointer
Published Jan 23, 2026 · Updated Jan 23, 2026
Memory corruption in the Linux Kernel ARP implementation allows local users to corrupt kernel memory during ARP packet creation. arp_create() caches an ARP-header pointer before dev_hard_header(), which can move skb->head and leave later ARP field writes aimed at stale storage. Triggering requires local access and a network-device path whose header builder moves the socket-buffer head; published assessments bound impact from a kernel crash to loss of confidentiality and integrity.
Summary
What happened
Memory corruption in the Linux Kernel ARP implementation allows local users to corrupt kernel memory during ARP packet creation. arp_create() caches an ARP-header pointer before dev_hard_header(), which can move skb->head and leave later ARP field writes aimed at stale storage. Triggering requires local access and a network-device path whose header builder moves the socket-buffer head; published assessments bound impact from a kernel crash to loss of confidentiality and integrity.
The record
- CVE
- CVE-2026-22988
- Published
- Jan 23, 2026
- Updated
- Jan 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2026CVE publishedPublication date reported by the CVE source.
- Jan 23, 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=1717357007db150c2d703f13f5695460e960f26c <029935507d0af6553c45380fbf6feecf756fd226
- Affected versionversion=17e7386234f740f3e7d5e58a47b5847ea34c3bc2 <e432dbff342b95fe44645f9a90fcf333c80f4b5e
- Affected versionversion=41a1a3140aff295dee8063906f70a514548105e8 <393525dee5c39acff8d6705275d7fcaabcfb7f0a
- Affected versionversion=5fe210533e3459197eabfdbf97327dacbdc04d60 <dd6ccec088adff4bdf33e2b2dd102df20a7128fa
- Affected versionversion=6.19-rc4
- Affected versionversion=91a2b25be07ce1a7549ceebbe82017551d2eec92 <949647e7771a4a01963fe953a96d81fba7acecf3
- Affected versionversion=adee129db814474f2f81207bd182bf343832a52e <70bddc16491ef4681f3569b3a2c80309a3edcdd1
- Affected versionversion=db5b4e39c4e63700c68a7e65fc4e1f1375273476 <c92510f5e3f82ba11c95991824a41e59a9c5ed81
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
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo