{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54027 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54027 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-54027 and fix it if it is affected.\n\nWhat it is: CVE-2023-54027 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-54027 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-54027/ (Markdown: https://insights.sbomify.com/CVE-2023-54027/index.md)","id":"CVE-2023-54027","markdown":"https://insights.sbomify.com/CVE-2023-54027/index.md","name":"CVE-2023-54027","record":{"aliases":["BELL-CVE-2023-54027","DEBIAN-CVE-2023-54027","GHSA-jwx3-9wmp-w467","UBUNTU-CVE-2023-54027"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can cause a kernel crash by creating a specific IIO dummy device via configfs, leading to a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: core: Prevent invalid memory access when there is no parent\n\nCommit 813665564b3d (\"iio: core: Convert to use firmware node handle\ninstead of OF node\") switched the kind of nodes to use for label\nretrieval in device registration.  Probably an unwanted change in that\ncommit was that if the device has no parent then NULL pointer is\naccessed.  This is what happens in the stock IIO dummy driver when a\nnew entry is created in configfs:\n\n  # mkdir /sys/kernel/config/iio/devices/dummy/foo\n  BUG: kernel NULL pointer dereference, address: ...\n  ...\n  Call Trace:\n  __iio_device_register\n  iio_dummy_probe\n\nSince there seems to be no reason to make a parent device of an IIO\ndummy device mandatory, let’s prevent the invalid memory access in\n__iio_device_register when the parent device is NULL.  With this\nchange, the IIO dummy driver works fine with configfs.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"iio: core: Prevent invalid memory access when there is no parent","id":"CVE-2023-54027","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"RDMA/rxe: Fix the error \"trying to register non-static key in rxe_cleanup_task\"","id":"CVE-2023-54028"},"packages":[],"prev":{"headline":"opp: Fix use-after-free in lazy_opp_tables after probe deferral","id":"CVE-2023-54026"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can cause a kernel crash by creating a specific IIO dummy device via configfs, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2023-54027/"}