{"api_version":"1","generated_at":"2026-09-15T05:44:03+00:00","cve":"CVE-2026-80940","urls":{"html":"https://cve.report/CVE-2026-80940","api":"https://cve.report/api/cve/CVE-2026-80940.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80940","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80940"},"summary":{"title":"wifi: rtw88: pci: fix resource leak on failed NAPI setup","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw88: pci: fix resource leak on failed NAPI setup\n\nrtw_pci_probe() allocates PCI resources through\nrtw_pci_setup_resource() before it sets up NAPI. If\nrtw_pci_napi_init() fails, the error path jumps straight to\nerr_pci_declaim and skips rtw_pci_destroy(), leaving the PCI\nresources allocated by rtw_pci_setup_resource() behind.\n\nAdd a dedicated cleanup label for the NAPI setup failure path so probe\ndestroys the PCI resources.\n\nThe bug was first flagged by an experimental analysis tool we are\ndeveloping for kernel memory-management bugs while analyzing current\nmainline kernels. The tool is still under development and is not yet\npublicly available. Manual inspection confirms that the bug is still\npresent in v7.1-rc7.\n\nAn x86_64 allyesconfig build showed no new warnings. As we do not have a\nsuitable rtw88 PCI board to test with, no runtime testing was able to be\nperformed.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:18:58","updated_at":"2026-09-11 20:18:58"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/b1596e212ab1739930b25b9d3daf6b5cd307b537","name":"https://git.kernel.org/stable/c/b1596e212ab1739930b25b9d3daf6b5cd307b537","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/34a505071d1ffc5ebf3dc3cd16d2a12b044bcc84","name":"https://git.kernel.org/stable/c/34a505071d1ffc5ebf3dc3cd16d2a12b044bcc84","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e779df4806cd29cbcca5c9dc0a1073662c76b889","name":"https://git.kernel.org/stable/c/e779df4806cd29cbcca5c9dc0a1073662c76b889","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/481fff9bda01720c70b19fb260808145a3f21594","name":"https://git.kernel.org/stable/c/481fff9bda01720c70b19fb260808145a3f21594","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80940","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80940","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d0bcb10e7b94861c714ab1e62c98bf8abaa37527 481fff9bda01720c70b19fb260808145a3f21594 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d0bcb10e7b94861c714ab1e62c98bf8abaa37527 34a505071d1ffc5ebf3dc3cd16d2a12b044bcc84 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d0bcb10e7b94861c714ab1e62c98bf8abaa37527 b1596e212ab1739930b25b9d3daf6b5cd307b537 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d0bcb10e7b94861c714ab1e62c98bf8abaa37527 e779df4806cd29cbcca5c9dc0a1073662c76b889 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.11","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.11 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.109 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80940","cve":"CVE-2026-80940","epss":"0.001680000","percentile":"0.063560000","score_date":"2026-09-14","updated_at":"2026-09-15 00:00:43"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/net/wireless/realtek/rtw88/pci.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"481fff9bda01720c70b19fb260808145a3f21594","status":"affected","version":"d0bcb10e7b94861c714ab1e62c98bf8abaa37527","versionType":"git"},{"lessThan":"34a505071d1ffc5ebf3dc3cd16d2a12b044bcc84","status":"affected","version":"d0bcb10e7b94861c714ab1e62c98bf8abaa37527","versionType":"git"},{"lessThan":"b1596e212ab1739930b25b9d3daf6b5cd307b537","status":"affected","version":"d0bcb10e7b94861c714ab1e62c98bf8abaa37527","versionType":"git"},{"lessThan":"e779df4806cd29cbcca5c9dc0a1073662c76b889","status":"affected","version":"d0bcb10e7b94861c714ab1e62c98bf8abaa37527","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/net/wireless/realtek/rtw88/pci.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.11"},{"lessThan":"6.11","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.109","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.109","versionStartIncluding":"6.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"6.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"6.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.11","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw88: pci: fix resource leak on failed NAPI setup\n\nrtw_pci_probe() allocates PCI resources through\nrtw_pci_setup_resource() before it sets up NAPI. If\nrtw_pci_napi_init() fails, the error path jumps straight to\nerr_pci_declaim and skips rtw_pci_destroy(), leaving the PCI\nresources allocated by rtw_pci_setup_resource() behind.\n\nAdd a dedicated cleanup label for the NAPI setup failure path so probe\ndestroys the PCI resources.\n\nThe bug was first flagged by an experimental analysis tool we are\ndeveloping for kernel memory-management bugs while analyzing current\nmainline kernels. The tool is still under development and is not yet\npublicly available. Manual inspection confirms that the bug is still\npresent in v7.1-rc7.\n\nAn x86_64 allyesconfig build showed no new warnings. As we do not have a\nsuitable rtw88 PCI board to test with, no runtime testing was able to be\nperformed."}],"providerMetadata":{"dateUpdated":"2026-09-11T19:42:13.084Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/481fff9bda01720c70b19fb260808145a3f21594"},{"url":"https://git.kernel.org/stable/c/34a505071d1ffc5ebf3dc3cd16d2a12b044bcc84"},{"url":"https://git.kernel.org/stable/c/b1596e212ab1739930b25b9d3daf6b5cd307b537"},{"url":"https://git.kernel.org/stable/c/e779df4806cd29cbcca5c9dc0a1073662c76b889"}],"title":"wifi: rtw88: pci: fix resource leak on failed NAPI setup","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80940","datePublished":"2026-09-11T19:42:13.084Z","dateReserved":"2026-08-26T14:34:25.803Z","dateUpdated":"2026-09-11T19:42:13.084Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:18:58","lastModifiedDate":"2026-09-11 20:18:58","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80940","Ordinal":"1","Title":"wifi: rtw88: pci: fix resource leak on failed NAPI setup","CVE":"CVE-2026-80940","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80940","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw88: pci: fix resource leak on failed NAPI setup\n\nrtw_pci_probe() allocates PCI resources through\nrtw_pci_setup_resource() before it sets up NAPI. If\nrtw_pci_napi_init() fails, the error path jumps straight to\nerr_pci_declaim and skips rtw_pci_destroy(), leaving the PCI\nresources allocated by rtw_pci_setup_resource() behind.\n\nAdd a dedicated cleanup label for the NAPI setup failure path so probe\ndestroys the PCI resources.\n\nThe bug was first flagged by an experimental analysis tool we are\ndeveloping for kernel memory-management bugs while analyzing current\nmainline kernels. The tool is still under development and is not yet\npublicly available. Manual inspection confirms that the bug is still\npresent in v7.1-rc7.\n\nAn x86_64 allyesconfig build showed no new warnings. As we do not have a\nsuitable rtw88 PCI board to test with, no runtime testing was able to be\nperformed.","Type":"Description","Title":"wifi: rtw88: pci: fix resource leak on failed NAPI setup"}]}}}