{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98711 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98711 is a vulnerability in Linux, published on 18 Oct 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-98711 and fix it if it is affected.\n\nWhat it is: CVE-2026-98711 is a vulnerability in Linux, published on 18 Oct 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-98711 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-98711/ (Markdown: https://insights.sbomify.com/CVE-2026-98711/index.md)","id":"CVE-2026-98711","markdown":"https://insights.sbomify.com/CVE-2026-98711/index.md","name":"CVE-2026-98711","record":{"aliases":["AZL-108893","BELL-CVE-2026-98711","DEBIAN-CVE-2026-98711","GHSA-rfqv-xwf2-63qv","UBUNTU-CVE-2026-98711"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A malicious Wi-Fi device can read up to 511 bytes of kernel heap memory per transmission due to an out-of-bounds read in the cw1200 driver.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\nwifi: cw1200: fix TX padding OOB read leaking heap data to device\n\nThe TX path rounds the transfer size up to the bus alignment\n(align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends\nthe padded length straight from the frame buffer, which has no room\nreserved for the padding.  cw1200_data_write() therefore reads past\nthe end of the frame and the bus transfer carries those bytes to the\ndevice.  A bogus device can collect up to 511 bytes of kernel heap\ndata per TX frame.\n\nThe RX path does not have this problem: it allocates the skb with\nthe aligned length (alloc_len) before reading.\n\nCompute the exact padding with the bus align_size() callback, make\nsure queued TX frames have tailroom for it, and zero the padding\nbytes before the transfer so nothing past the frame is exposed.\n\nThis is not expected to change driver behavior on most cases: frame\ncontents and transfer sizes are unchanged, only the content of the\npadding bytes (previously undefined stale memory, now zero), which\nthe device never reads since the WSM header carries the real frame\nlength.  The skb expansion can only fail under memory exhaustion,\nin which case the frame is dropped like on the existing error paths\nof cw1200_tx().\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.","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: cw1200: fix TX padding OOB read leaking heap data to device","id":"CVE-2026-98711","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"KVM: arm64: vgic: Take a refcount on IRQs referenced by last_lr_irq","id":"CVE-2026-98712"},"packages":[],"prev":{"headline":"wifi: iwlegacy: 3945: free EEPROM data on remove","id":"CVE-2026-98710"},"products":["Linux"],"published":"2026-10-18","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-21","vendors":["Linux"]},"summary":"A malicious Wi-Fi device can read up to 511 bytes of kernel heap memory per transmission due to an out-of-bounds read in the cw1200 driver.","url":"https://insights.sbomify.com/CVE-2026-98711/"}