{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93124 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93124 is a vulnerability in Linux, published on 17 Sep 2026. 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-2026-93124 and fix it if it is affected.\n\nWhat it is: CVE-2026-93124 is a vulnerability in Linux, published on 17 Sep 2026. 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-2026-93124 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-2026-93124/ (Markdown: https://insights.sbomify.com/CVE-2026-93124/index.md)","id":"CVE-2026-93124","markdown":"https://insights.sbomify.com/CVE-2026-93124/index.md","name":"CVE-2026-93124","record":{"aliases":["DEBIAN-CVE-2026-93124","GHSA-jvjx-cfgv-jw7v","UBUNTU-CVE-2026-93124"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A local attacker with high privileges can trigger a kernel crash by force-binding the asus-wireless driver to a device without an ACPI companion.","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\nplatform/x86: asus-wireless: Fail probe when there is no ACPI match\n\nEvery platform driver can be forced to match a device that does not match\nits list of device IDs because of device_match_driver_override(), so\nplatform drivers that rely on the existence of a device ACPI companion\nobject need to verify its presence.\n\nasus_wireless_probe() returns success when acpi_match_acpi_device()\nfinds no match, leaving behind an input device that never reports\nanything because the notify handler is not installed.  Worse, when the\ndriver is force-bound to a device without an ACPI companion, probe\nstill succeeds and stores a NULL companion pointer, which\nasus_wireless_remove() later passes to acpi_dev_remove_notify_handler(),\nleading to a NULL pointer dereference on unbind.\n\nReturn -ENODEV when the device does not match the ID table.  This also\ncovers the missing-companion case, because acpi_match_acpi_device()\nrejects a NULL device.  Perform the check before allocating any driver\nstate, instead of after the input device has already been registered.","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":"platform/x86: asus-wireless: Fail probe when there is no ACPI match","id":"CVE-2026-93124","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max","id":"CVE-2026-93125"},"packages":[],"prev":{"headline":"serial: qcom-geni: do not advance stale DMA completions","id":"CVE-2026-93123"},"products":["Linux"],"published":"2026-09-17","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-10-19","vendors":["Linux"]},"summary":"A local attacker with high privileges can trigger a kernel crash by force-binding the asus-wireless driver to a device without an ACPI companion.","url":"https://insights.sbomify.com/CVE-2026-93124/"}