Kernel crash via unchecked device-match dereference
Published Dec 30, 2025 · Updated Dec 30, 2025
NULL pointer dereference in Linux kernel meson_sm firmware-driver probing in affected releases from 5.5 allows attackers to crash the kernel. The meson_sm_probe function accesses the data member of of_match_device() without first checking whether the returned match pointer is NULL. The fault requires platform-driver probing to find no matching device-tree entry; published sources identify no attacker-controlled path to that state, so exposure is hardware and configuration dependent.
Summary
What happened
NULL pointer dereference in Linux kernel meson_sm firmware-driver probing in affected releases from 5.5 allows attackers to crash the kernel. The meson_sm_probe function accesses the data member of of_match_device() without first checking whether the returned match pointer is NULL. The fault requires platform-driver probing to find no matching device-tree entry; published sources identify no attacker-controlled path to that state, so exposure is hardware and configuration dependent.
The record
- CVE
- CVE-2023-54304
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=525ae72d9f0b5cf027f1c78c84e41c90e86df026 <fba9c24c196310546f13c77ff66d0741155fa771
- Affected versionversion=5.5
- Affected versionversion=8cde3c2153e8f57be884c0e73f18bc4de150e870 <2d6c4a1a4e6678cb98dd57964f133a995ecc91c1
- Affected versionversion=8cde3c2153e8f57be884c0e73f18bc4de150e870 <502dfc5875bab9ae5d6a2939146c2c5e5683be40
- Affected versionversion=8cde3c2153e8f57be884c0e73f18bc4de150e870 <68f3209546b5083f8bffa46f7173cc05191eace1
- Affected versionversion=8cde3c2153e8f57be884c0e73f18bc4de150e870 <9f4017cac70c04090dd4f672e755d6c875af67d8
- Affected versionversion=8cde3c2153e8f57be884c0e73f18bc4de150e870 <bd3a6b6d5dd863dbbe17985c7612159cf4533cad
- Affected versionversion=8cde3c2153e8f57be884c0e73f18bc4de150e870 <f2ed165619c16577c02b703a114a1f6b52026df4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo