CVE-2026-98027
What it is
In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6xxx: bound the policy rule dump by the caller's buffer size mv88e6xxx_get_rxnfc() uses rxnfc->rule_cnt as the write index while dumping the policy IDR, clobbering the input value before it has been looked at. That input is the number of entries the caller had room for. ETHTOOL_GRXCLSRLALL requires no CAP_NET_ADMIN and the ioctl sizes the buffer from the rule_cnt userspace passes in, so once an admin has installed policy rules any user can ask for fewer slots than there are rules and run off the end of the allocation. A rule_cnt of 0 leaves the buffer pointer NULL and the walk dereferences it. Count into a local so the caller's limit survives the walk, and stop with -EMSGSIZE once it is reached.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.0 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Received
Attack profile CVSS 3.1 · 7.0
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-98027.md and follow it. Check whether this project is affected by CVE-2026-98027. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/01124cd2cf4b71755b1130ac82d78dcfbd5d69e3
- https://git.kernel.org/stable/c/44cd4674d9aa5bdf793b8a8b481c9e8536ed6070
- https://git.kernel.org/stable/c/609c4378f212cf580aae02250f1146caf63d873f
- https://git.kernel.org/stable/c/7a683c2b062810bca203e41866389daf387c235b
- https://git.kernel.org/stable/c/7e4bfc5f0b66feb22cba821303fc25ca22cd0887
- https://git.kernel.org/stable/c/b1fffc273112e7284c5b705e186b43b5770cd3d5
- https://git.kernel.org/stable/c/c5b5c52b6524c9fb50def2260baac745c095ec3a
- https://git.kernel.org/stable/c/cda5ac8fe8ac8e80b1703ebb8c4250726fc19739