{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74554 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74554 is a high-severity memory corruption 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-74554 and fix it if it is affected.\n\nWhat it is: CVE-2026-74554 is a high-severity memory corruption 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-74554 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-74554/ (Markdown: https://insights.sbomify.com/CVE-2026-74554/index.md)","id":"CVE-2026-74554","markdown":"https://insights.sbomify.com/CVE-2026-74554/index.md","name":"CVE-2026-74554","record":{"aliases":["DEBIAN-CVE-2026-74554","GHSA-m2x9-5x38-cjm5","UBUNTU-CVE-2026-74554"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel WiFi driver","requires_auth":"none","summary":"An out-of-bounds write in the ath12k WiFi driver corrupts memory, potentially causing denial of service or code execution in the Linux kernel.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: fix out-of-bounds clear_bit in ath12k_mac_dp_peer_cleanup()\n\nath12k_mac_dp_peer_cleanup() clears the ML peer ID slot on the\nfree_ml_peer_id_map bitmap by indexing it with dp_peer-\u003epeer_id. That is\nwrong: dp_peer-\u003epeer_id for an MLO peer always carries the\nATH12K_PEER_ML_ID_VALID bit (BIT(13)), so clear_bit() is invoked with\nindex \u003e= 0x2000, which is far outside the bitmap of ATH12K_MAX_MLO_PEERS\n(256) bits and corrupts memory adjacent to ah-\u003efree_ml_peer_id_map. The\nintended bitmap entry also never gets cleared, so subsequent\nath12k_peer_ml_alloc() calls eventually run out of IDs.\n\nThe ID without the VALID bit is what ath12k_peer_ml_alloc() returned and\nis stored in ahsta-\u003eml_peer_id. Use that instead.\n\nWhile there, also reset ahsta-\u003eml_peer_id to ATH12K_MLO_PEER_ID_INVALID so\nthe bitmap and ahsta-\u003eml_peer_id stay in sync.\n\nTested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3","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":"wifi: ath12k: fix out-of-bounds clear_bit in ath12k_mac_dp_peer_cleanup()","id":"CVE-2026-74554","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race","id":"CVE-2026-74555"},"packages":[],"prev":{"headline":"hwmon: (nct6775-core) Fix number of temperature registers for NCT6116","id":"CVE-2026-74553"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"An out-of-bounds write in the ath12k WiFi driver corrupts memory, potentially causing denial of service or code execution in the Linux kernel.","url":"https://insights.sbomify.com/CVE-2026-74554/"}