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

In the Linux kernel, the following vulnerability has been resolved: net: fec: Better handle pm_runtime_get() failing in .remove() In the (unlikely) event that pm_runtime_get() (disguised as pm_runtime_resume_and_get()) fails, the remove callback returned an error early. The problem with this is that the driver core ignores the error value and continues removing the device. This results in a resource leak. Worse the devm allocated resources are freed and so if a callback of the driver is called later the register mapping is already gone which probably results in a crash.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-09-17	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-09-17

—

0.02%

—

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]
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	134c704f-9b21-4f2e-91b3-4a467353bcc0

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]

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

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2023-53308

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2023-53308 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-53308
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2023-53308
`suse`	medium	CVE-2023-53308 severity moderate: SUSE including 266 source package names (amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, amazon/suse-sles-15-sp1-chost-byos-v20220127-hvm-ssd-x86_64, …), 475 product×package rows across 51 product lines (Image SLES12-SP5-Azure-BYOS, Image SLES12-SP5-Azure-HPC-BYOS, … (51 product lines)): Known Affected 231, Known Not Affected 174, Fixed 70.	https://www.suse.com/security/cve/CVE-2023-53308/
`ubuntu`	medium	CVE-2023-53308 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 159, released 138, not-affected 84, needed 15, needs-triage 1.	https://ubuntu.com/security/CVE-2023-53308

Affected software / configurations for CVE-2023-53308

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.9.206, < 4.10	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.14.158, < 4.14.316	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.19.88, < 4.19.284	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.3.15, < 5.4	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.4.1, < 5.4.244	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.181	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.113	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.1.30	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.3.4	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	5.4	cpe:2.3:o:linux:linux_kernel:5.4:-::::::
linux	linux_kernel	6.4	cpe:2.3:o:linux:linux_kernel:6.4:rc1::::::
linux	linux_kernel	6.4	cpe:2.3:o:linux:linux_kernel:6.4:rc2::::::

References for CVE-2023-53308

URL	Tags
https://git.kernel.org/stable/c/83996d317b1deddc85006376082e8886f55aa709	Patch
https://git.kernel.org/stable/c/9407454a9b18bbeff216e8ecde87ffb2171e9ccf	Patch
https://git.kernel.org/stable/c/b22b514209ff8c4287abb853399890ab97e1b5ca	Patch
https://git.kernel.org/stable/c/be85912c36ddca3e8b2eef1b5392cd8db6bdb730	Patch
https://git.kernel.org/stable/c/c1bc2870f14e526a01897e14c747a0a0ca125231	Patch
https://git.kernel.org/stable/c/d52a0cca591e899d4e5c8ab19e067b4c6b7d104f	Patch
https://git.kernel.org/stable/c/e02d8d5b1602689b98d9b91550a11b9b57baedbe	Patch
https://git.kernel.org/stable/c/f816b9829b19394d318e01953aa3b2721bca040d	Patch

URL

CVE-2023-53308 | net: fec: Better handle pm_runtime_get() failing in .remove()

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

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

Weakness enumeration for CVE-2023-53308

OS Trackers for CVE-2023-53308

Affected software / configurations for CVE-2023-53308

References for CVE-2023-53308