CVE-2023-53000
What it is
In the Linux kernel, the following vulnerability has been resolved: netlink: prevent potential spectre v1 gadgets Most netlink attributes are parsed and validated from __nla_validate_parse() or validate_nla() u16 type = nla_type(nla); if (type == 0 || type > maxtype) { /* error or continue */ } @type is then used as an array index and can be used as a Spectre v1 gadget. array_index_nospec() can be used to prevent leaking content of kernel memory to malicious users. This should take care of vast majority of netlink uses, but an audit is needed to take care of others where validation is not yet centralized in core netlink functions.
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.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- 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.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-129
- Record status
- Analyzed
Affected
- Linux Kernel < 5.4.231
- Linux Kernel < 5.10.166
- Linux Kernel < 5.15.91
- Linux Kernel < 6.1.9
- Linux Kernel 6.2
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/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-2023-53000.md and follow it. Check whether this project is affected by CVE-2023-53000. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/3e5082b1c66c7783fbcd79b5b178573230e528ff
- https://git.kernel.org/stable/c/41b74e95f297ac360ca7ed6bf200100717cb6c45
- https://git.kernel.org/stable/c/539ca5dcbc91134bbe2c45677811c31d8b030d2d
- https://git.kernel.org/stable/c/992e4ff7116a77968039277b5d6aaa535c2f2184
- https://git.kernel.org/stable/c/f0950402e8c76e7dcb08563f1b4e8000fbc62455
References
- https://git.kernel.org/stable/c/3e5082b1c66c7783fbcd79b5b178573230e528ff
- https://git.kernel.org/stable/c/41b74e95f297ac360ca7ed6bf200100717cb6c45
- https://git.kernel.org/stable/c/539ca5dcbc91134bbe2c45677811c31d8b030d2d
- https://git.kernel.org/stable/c/992e4ff7116a77968039277b5d6aaa535c2f2184
- https://git.kernel.org/stable/c/f0950402e8c76e7dcb08563f1b4e8000fbc62455