Linux Kernel up to 7.2.6/7.3-rc2 erofs encoding error

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in Linux Kernel up to 7.2.6/7.3-rc2. It has been rated as very critical. Affected by this vulnerability is an unknown functionality of the component erofs. This manipulation causes encoding error. The identification of this vulnerability is CVE-2026-98005. The attack can only be executed locally. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in Linux Kernel up to 7.2.6/7.3-rc2 and classified as very critical. Affected by this vulnerability is an unknown function of the component erofs. The manipulation with an unknown input leads to a encoding error vulnerability. The CWE definition for the vulnerability is CWE-172. The product does not properly encode or decode the data, resulting in unexpected values. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inode_share cache key components Previously, inode_share keys were encoded as follows: fingerprint || domain_id It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won't be parsed as part of a domain ID. Change the key encoding as follows: domain_id || '\0' || fingerprint Since domain_id is a NUL-terminated string, this makes the in-memory key indices unambiguous.
It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-98005 since 09/25/2026. The exploitation appears to be easy. Attacking locally is a requirement. Additional levels of successful authentication are needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/25/2026).
Upgrading to version 7.2.7 or 7.3-rc3 eliminates this vulnerability. Applying the patch 16322a67336cfeea0af4b05206ef8d0e0eda55bb/96bf9831fbf423b8104f7948cd8fe7007ecfb46c is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 7.8
VulDB Base Score: 8.2
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Encoding errorCWE: CWE-172
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 7.2.7/7.3-rc3
Patch: 16322a67336cfeea0af4b05206ef8d0e0eda55bb/96bf9831fbf423b8104f7948cd8fe7007ecfb46c
Timeline
09/25/2026 Advisory disclosed09/25/2026 CVE reserved
09/25/2026 VulDB entry created
09/25/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-98005 (🔒)
GCVE (CVE): GCVE-0-2026-98005
GCVE (VulDB): GCVE-100-410179
Entry
Created: 09/25/2026 15:24Changes: 09/25/2026 15:24 (58)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.