CVE-2023-54027
Last modified
CVE-2023-54027 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: iio: core: Prevent invalid memory access when there is no parent Commit 813665564b3d ("iio: core: Convert to use firmware node handle instead of OF node") switched the kind of nodes to use for label retrieval in device registration. Probably an unwanted change in that commit was that if the device has no parent then NULL pointer is accessed. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: iio: core: Prevent invalid memory access when there is no parent Commit 813665564b3d ("iio: core: Convert to use firmware node handle instead of OF node") switched the kind of nodes to use for label retrieval in device registration. Probably an unwanted change in that commit was that if the device has no parent then NULL pointer is accessed. This is what happens in the stock IIO dummy driver when a new entry is created in configfs: # mkdir /sys/kernel/config/iio/devices/dummy/foo BUG: kernel NULL pointer dereference, address: ... ... Call Trace: __iio_device_register iio_dummy_probe Since there seems to be no reason to make a parent device of an IIO dummy device mandatory, let’s prevent the invalid memory access in __iio_device_register when the parent device is NULL. With this change, the IIO dummy driver works fine with configfs.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 813665564b3d7c74412fe2877520f1d254ce948a, < 312f04ede209f0a186799fe8e64a19b49700d5dc; >= 813665564b3d7c74412fe2877520f1d254ce948a, < a4b34cccff14ce74bb7d77fbfd56e7c9d7c28a97; >= 813665564b3d7c74412fe2877520f1d254ce948a, < b2a69969908fcaf68596dfc04369af0fe2e1d2f7 |
| Linux | Linux | 5.19 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-54027?
How severe is CVE-2023-54027?
How do I fix CVE-2023-54027?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-54021In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54022In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54023In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54024In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54025In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54026In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54028In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54029Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-5403Server hostname translation to IP address manipulation which…8.1
- CVE-2023-54030In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54031In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54032In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2023-54027?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
