CVE-2023-53250

firmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle

MEDIUM
5.5
CVSS Score
Published: September 15, 2025 at 02:46 PM UTC
Updated: June 17, 2026 at 06:44 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: firmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle KASAN reported a null-ptr-deref error: KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] CPU: 0 PID: 1373 Comm: modprobe Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) RIP: 0010:dmi_sysfs_entry_release ... Call Trace: <TASK> kobject_put dmi_sysfs_register_handle (drivers/firmware/dmi-sysfs.c:540) dmi_sysfs dmi_decode_table (drivers/firmware/dmi_scan.c:133) dmi_walk (drivers/firmware/dmi_scan.c:1115) dmi_sysfs_init (drivers/firmware/dmi-sysfs.c:149) dmi_sysfs do_one_initcall (init/main.c:1296) ... Kernel panic - not syncing: Fatal exception Kernel Offset: 0x4000000 from 0xffffffff81000000 ---[ end Kernel panic - not syncing: Fatal exception ]--- It is because previous patch added kobject_put() to release the memory which will call dmi_sysfs_entry_release() and list_del(). However, list_add_tail(entry->list) is called after the error block, so the list_head is uninitialized and cannot be deleted. Move error handling to after list_add_tail to fix this.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.14.283v ≥ 4.19.247v ≥ 4.9.318v ≥ 5.10.122v ≥ 5.17.15v ≥ 5.18.4v ≥ 5.4.1984.14.283 ≤ v < 4.154.19.247 ≤ v < 4.204.9.318 ≤ v < 4.105.10.122 ≤ v < 5.115.15.47 ≤ v < 5.15.995.17.15 ≤ v < 5.185.18.4 ≤ v < 5.195.18.4 ≤ v < 6.1.165.19 ≤ v < 6.1.165.19 ≤ v < 6.2.35.19 ≤ v < 6.35.4.198 ≤ v < 5.56.2 ≤ v < 6.2.33ba359ebe914ac3f8c6c832b28007c14c39d37664.14.2834.19.2474.9.3185.10.1225.15.475.17.155.18.45.195.4.198660ba678f9998aca6db74f2dd912fa5124f0fa31985706bd3bbeffc8737bc05965ca8d24837bc7dba724634b2a49f6ff0177a9e19a5a92fc1545e1b7a9bfb37d6ba7c376b0d53337a4c5f5ff324bd725c66cc3c62870a27ea8f060a7e4c1ad8d26dd3f0dec752973aa721ee281d5441e497364637c626c7bed38d04342dfbe9e5aca745c8b5eb4188a74f0effdffa4ad8f6bf1ece877edfb807f2b2c729d8578
Vendor states this is fixed in 18e126e97c961f7a93823795c879d7c085fe5098 (fixed)
Vendor states this is fixed in 5d0492d1d934642bdfd2057acc1b56f4b57be465 (fixed)
Vendor states this is fixed in b4fe158259fb5fead52ff2b55841ec5c39492604 (fixed)
Vendor states this is fixed in e851996b32264e78a10863c2ac41a8689d7b9252 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.15.99 (unaffected)
Affected range stops below 5.18, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.19 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.16 (unaffected)
Vendor states this is fixed in 6.2.3 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/18e126e97c961f7a93823795c879d7c085fe5098
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5d0492d1d934642bdfd2057acc1b56f4b57be465
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b4fe158259fb5fead52ff2b55841ec5c39492604
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e851996b32264e78a10863c2ac41a8689d7b9252

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card