CVE-2023-54027

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.

Package Linux Kernel
Published 2025-12-24
Last modified 2026-04-15
Patch available
Yes

Affected versions

Linux kernel versions 5.19 and later are affected. Fixed in 6.1.46, 6.4.11, 6.5 and their respective stable series.

Affected from
≥ 5.19
Fixed in
✓ 6.1.46 6.1.x ✓ 6.4.11 6.4.x ✓ 6.5

References

The following references provide additional information about CVE-2023-54027 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2023-54027?

    CVE-2023-54027 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.19 onward and has been patched in 6.1.46, 6.4.11 and 6.5. CVE-2023-54027 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2023-54027?

    Yes — CVE-2023-54027 has been patched. Fixed versions include 6.1.46, 6.4.11 and 6.5. If you are running Linux kernel 5.19 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2023-54027 actively exploited?

    No — CVE-2023-54027 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.