Kernel memory corruption via unchecked rule count
Published Oct 1, 2025 · Updated Aug 5, 2026
Out-of-bounds write in the Linux kernel 5.2 through 6.6-rc1 allows local users to corrupt kernel memory through an ethtool ioctl. mvpp2_ethtool_get_rxnfc allocates its rules buffer from the user-controlled rule_cnt, then writes the configured flow-rule list without rejecting a count smaller than the actual list. Any local user can issue the whitelisted SIOCETHTOOL request, but the path requires an mvpp2 interface with persistent ntuple flow-steering rules; exploitation can crash the kernel or alter or disclose kernel memory.
Summary
What happened
Out-of-bounds write in the Linux kernel 5.2 through 6.6-rc1 allows local users to corrupt kernel memory through an ethtool ioctl. mvpp2_ethtool_get_rxnfc allocates its rules buffer from the user-controlled rule_cnt, then writes the configured flow-rule list without rejecting a count smaller than the actual list. Any local user can issue the whitelisted SIOCETHTOOL request, but the path requires an mvpp2 interface with persistent ntuple flow-steering rules; exploitation can crash the kernel or alter or disclose kernel memory.
The record
- CVE
- CVE-2023-53495
- Published
- Oct 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
- Oct 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=5.2
- Affected versionversion=90b509b39ac9b09be88eb641c7a3abd8de06b698 <349638f7e5d3c7d328565587bb7b0454bbee02e2
- Affected versionversion=90b509b39ac9b09be88eb641c7a3abd8de06b698 <51fe0a470543f345e3c62b6798929de3ddcedc1d
- Affected versionversion=90b509b39ac9b09be88eb641c7a3abd8de06b698 <5bb09dddc724c5f7c4dc6dd3bfebd685eecd93e8
- Affected versionversion=90b509b39ac9b09be88eb641c7a3abd8de06b698 <61054a8ddb176b155a8f2bacdfefb3727187f5d9
- Affected versionversion=90b509b39ac9b09be88eb641c7a3abd8de06b698 <625b70d31dd4df4b96b3ddcbe251debb33bd67f5
- Affected versionversion=90b509b39ac9b09be88eb641c7a3abd8de06b698 <ba6673824efa3dc198b04a54e69dce480066d7d9
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.
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