CVE-2026-98160 — In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs…
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init() padapter->HalData is allocated via vzalloc(), but incorrectly freed using kfree() in the rtw_sdio_if1_init() error path. Using kfree() to release this vmalloc-backed buffer can lead to memory corruption. Use rtw_hal_data_deinit() to pair the free correctly and free HalData with vfree(). The bug was first flagged by an experimental static analysis tool we are developing for kernel memory-management bugs. Manual inspection confirms that the issue is still present in current mainline. An x86_64 allyesconfig build showed no new warnings. As we do not have suitable RTL8723BS SDIO hardware to test with, no runtime testing was able to be performed.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux Kernel | ≥ 4.12 and < 5.10.270≥ 5.11 and < 5.15.221≥ 5.16 and < 6.1.188≥ 6.2 and < 6.6.157≥ 6.7 and < 6.12.110≥ 6.13 and < 6.18.52≥ 6.19 and < 7.2.6 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/ff6d1ba247b5c62bdb678f1069abc86ad88a1402
- git.kernel.org/stable/c/d6158333d630a1b21d8914feaf77a6f5deb185d9
- git.kernel.org/stable/c/423574feaed192063ef0cd0813fb85425f39e539
- git.kernel.org/stable/c/264676418b726baca7be49171e306b6aa05cceb0
- git.kernel.org/stable/c/911190f0b9511c3c81f2f2484414c1ae26f636b3
- git.kernel.org/stable/c/737c928ff5092d7e55128a232c231248fc993777
- git.kernel.org/stable/c/6c017ab2b0e1b60b5be94636c94720347213d78b
- git.kernel.org/stable/c/4520d673d49dabfd42c008a33889251025f7d6d5
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-98164 KVM: x86/mmu: Check write tracking in all address spaces 16d
- High CVE-2026-98163 cgroup: Avoid iteration of dying tasks with zero refcount 19d
- Medium CVE-2026-98162 smb/server: fix tree connection leak in smb2_tree_connect() 20d
- Medium CVE-2026-98161 Improper Check for Unusual or Exceptional Conditions in Linux Linux Kernel 20d
- Medium CVE-2026-100079 Missing Release of Resource after Effective Lifetime in Linux Linux Kernel 20d
- Critical CVE-2026-100075 In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Fix… 20d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98160 is "In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs…", rated Medium. It affects Linux Kernel (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.