Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-54027iio: core: Prevent invalid memory access when there is no parent

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 813665564b3d7c74412fe2877520f1d254ce948a – < 312f04ede209f0a186799fe8e64a19b49700d5dc
    • affected 813665564b3d7c74412fe2877520f1d254ce948a – < a4b34cccff14ce74bb7d77fbfd56e7c9d7c28a97
    • affected 813665564b3d7c74412fe2877520f1d254ce948a – < b2a69969908fcaf68596dfc04369af0fe2e1d2f7
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.46 – ≤ 6.1.*
    • unaffected 6.4.11 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54027 badge
[![CVE-2023-54027](https://cveledger.app/badge/CVE-2023-54027.svg)](https://cveledger.app/cve/CVE-2023-54027)

Record last updated .