{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80743 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80743 is a vulnerability in Linux, published on 3 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-80743 and fix it if it is affected.\n\nWhat it is: CVE-2026-80743 is a vulnerability in Linux, published on 3 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-80743 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-80743/ (Markdown: https://insights.sbomify.com/CVE-2026-80743/index.md)","id":"CVE-2026-80743","markdown":"https://insights.sbomify.com/CVE-2026-80743/index.md","name":"CVE-2026-80743","record":{"aliases":["AZL-99077","BELL-CVE-2026-80743","DEBIAN-CVE-2026-80743","GHSA-x2vc-grmm-48qg","UBUNTU-CVE-2026-80743"],"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 race condition in the Xilinx formatter PCM driver causes a null pointer dereference and kernel crash if an interrupt occurs during 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\nASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers\n\nThe irq handlers take a struct device pointer and call\ndev_get_drvdata() to obtain the driver data.  However, the driver\ndata is only set at the end of probe, after devm_request_irq(),\nso an interrupt taken in between causes the handlers to pass a\nNULL pointer to readl() and crash.\n\nPass the private data directly as the devm_request_irq() argument\ninstead of the device pointer, matching what the handlers expect.","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":"ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers","id":"CVE-2026-80743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"netfilter: nf_tables_offload: suppress WARN_ON_ONCE for ENOMEM in abort path","id":"CVE-2026-80744"},"packages":[],"prev":{"headline":"af_packet: Don't send zero-byte data in tpacket_snd().","id":"CVE-2026-80742"},"products":["Linux"],"published":"2026-09-03","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-09-03","vendors":["Linux"]},"summary":"A race condition in the Xilinx formatter PCM driver causes a null pointer dereference and kernel crash if an interrupt occurs during probe.","url":"https://insights.sbomify.com/CVE-2026-80743/"}