{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72424 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72424 is a vulnerability in Linux, published on 15 Aug 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-72424 and fix it if it is affected.\n\nWhat it is: CVE-2026-72424 is a vulnerability in Linux, published on 15 Aug 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-72424 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-72424/ (Markdown: https://insights.sbomify.com/CVE-2026-72424/index.md)","id":"CVE-2026-72424","markdown":"https://insights.sbomify.com/CVE-2026-72424/index.md","name":"CVE-2026-72424","record":{"aliases":["BELL-CVE-2026-72424","DEBIAN-CVE-2026-72424","GHSA-cg6j-2hpf-xr59","UBUNTU-CVE-2026-72424"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A NULL pointer dereference in the Linux kernel RTC driver can cause a system crash when a shared IRQ is triggered during device probe.","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\nrtc: msc313: fix NULL deref in shared IRQ handler at probe\n\nmsc313_rtc_probe() calls devm_request_irq() with IRQF_SHARED and\n\u0026pdev-\u003edev as the cookie, but platform_set_drvdata() is only called\nlater after the clock setup. With a shared IRQ line, another device\non the same line can trigger the handler in that window. The\nhandler does dev_get_drvdata() on the cookie, gets NULL, and\ndereferences priv-\u003ertc_base in interrupt context.\n\nPass priv as the cookie directly so the handler reads it from\ndev_id without the lookup, removing the dependency on probe order.","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":"rtc: msc313: fix NULL deref in shared IRQ handler at probe","id":"CVE-2026-72424","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs()","id":"CVE-2026-72425"},"packages":[],"prev":{"headline":"bpf: Guard conntrack opts error writes","id":"CVE-2026-72423"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Linux kernel RTC driver can cause a system crash when a shared IRQ is triggered during device probe.","url":"https://insights.sbomify.com/CVE-2026-72424/"}