PatchSiren cyber security CVE debrief
CVE-2026-98160 Linux CVE debrief
A vulnerability in the Linux kernel's staging/rtl8723bs driver can lead to memory corruption due to a mismatched free of HalData in the rtw_sdio_if1_init() error path. The bug was introduced because padapter->HalData, allocated via vzalloc(), was incorrectly freed using kfree(). This issue can cause system instability and potential denial-of-service (DoS) or privilege escalation. Linux kernel developers and maintainers should assess exposure and prioritize verification of affected versions and configurations. The bug was first flagged by an experimental static analysis tool for kernel memory-management bugs. Manual inspection confirms that the issue is still present in current main
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Linux kernel developers and maintainers, system administrators, and security teams responsible for Linux kernel-based systems should assess exposure and prioritize verification of affected versions and configurations.
Why it matters
A vulnerability in the Linux kernel's staging/rtl8723bs driver can lead to memory corruption due to a mismatched free of HalData in the rtw_sdio_if1_init() error path. Linux kernel developers and maintainers should assess exposure and prioritize verification of affected versions and configurations.
- Memory corruption can lead to system crashes or instability
- Potential for denial-of-service (DoS) or privilege escalation
- Verification of affected versions and configurations is necessary
- Patching or mitigation is required to prevent exploitation
Technical summary
The Linux kernel's staging/rtl8723bs driver has a vulnerability due to a mismatched free of HalData in the rtw_sdio_if1_init() error path. The bug was introduced because padapter->HalData, allocated via vzalloc(), was incorrectly freed using kfree(). To fix the issue, rtw_hal_data_deinit() should be used to pair the free correctly and free HalData with vfree(). This requires careful review of affected product deployments and configurations to ensure proper patching or mitigation. The vulnerability can lead to memory corruption, system crashes, or instability, and potentially allow for denial-of-service (DoS) or privilege escalation.
Defensive priority
Linux kernel developers and maintainers should assess exposure and prioritize verification of affected versions and configurations. System administrators and security teams should monitor for potential memory corruption issues.
Recommended defensive actions
- Review and verify affected Linux kernel versions and configurations
- Assess exposure and prioritize patching or mitigation
- Monitor system logs for potential memory corruption issues
- Perform thorough vulnerability assessment
- Implement compensating controls for exposed systems
- Track exceptions and retest remediated assets
- Review vendor-provided patches and advisories
Evidence notes
The bug was first flagged by an experimental static analysis tool for kernel memory-management bugs. Manual inspection confirms that the issue is still present in current mainline. No runtime testing was performed due to lack of suitable RTL8723BS SDIO hardware.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-98160 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-98160
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-98160 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-98160
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/264676418b726baca7be49171e306b6aa05cceb0
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/423574feaed192063ef0cd0813fb85425f39e539
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/4520d673d49dabfd42c008a33889251025f7d6d5
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6c017ab2b0e1b60b5be94636c94720347213d78b
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/737c928ff5092d7e55128a232c231248fc993777
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/911190f0b9511c3c81f2f2484414c1ae26f636b3
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d6158333d630a1b21d8914feaf77a6f5deb185d9
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/ff6d1ba247b5c62bdb678f1069abc86ad88a1402
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.