CVE-2023-53000 [High] | Information Disclosure in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-07	0.06%	0.02%	-0.04%
2	2026-05-05	0.03%	0.06%	+0.03%
3	2025-11-21	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-07

0.06%

0.02%

-0.04%

2026-05-05

0.03%

0.06%

+0.03%

2025-11-21

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2023-53000

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2023-53000 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2023-53000
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2023-53000
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2023-53000/
`ubuntu`	medium	CVE-2023-53000 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 150, released 138, not-affected 98, needed 19, needs-triage 1.	https://ubuntu.com/security/CVE-2023-53000

Affected software / configurations for CVE-2023-53000

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 2.6.15, < 5.4.231	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.166	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.91	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.1.9	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc1::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc2::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc3::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc4::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc5::::::

References for CVE-2023-53000

URL	Tags
https://git.kernel.org/stable/c/3e5082b1c66c7783fbcd79b5b178573230e528ff	Patch
https://git.kernel.org/stable/c/41b74e95f297ac360ca7ed6bf200100717cb6c45	Patch
https://git.kernel.org/stable/c/539ca5dcbc91134bbe2c45677811c31d8b030d2d	Patch
https://git.kernel.org/stable/c/992e4ff7116a77968039277b5d6aaa535c2f2184	Patch
https://git.kernel.org/stable/c/f0950402e8c76e7dcb08563f1b4e8000fbc62455	Patch

URL

CVE-2023-53000 | netlink: prevent potential spectre v1 gadgets

Exploit prediction scoring system (EPSS) score for CVE-2023-53000

Common vulnerability scoring system (CVSS) metrics for CVE-2023-53000

Weakness enumeration for CVE-2023-53000

OS Trackers for CVE-2023-53000

Affected software / configurations for CVE-2023-53000

References for CVE-2023-53000