[CVE-2026-98872][LOW] freevxfs: don't BUG() on unknown typed-extent type [ Upstream

[CVE-2026-98872][LOW] freevxfs: don't BUG() on unknown typed-extent type [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98872
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: freevxfs: don't BUG() on unknown typed-extent type [ Upstream
Commit: fe40a19d571cbb584eea46038ee919d8712b2d2c
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fe40a19d571cbb584eea46038ee919d8712b2d2c
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98872
Analysis date: Mon, 26 Oct 2026 22:22:12 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
Malformed FreeVxFS metadata can make a privileged FIBMAP operation execute `BUG()`, causing an Oops or panic without a demonstrated memory-corruption or authorization primitive.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-98872 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98872

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-98872	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98872 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=0 LEGACY=LOW RESULT=DIFF TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (final Legacy and Aegis differ; FINAL: LOW, Aegis: MODERATE_KPANIC)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';CWE-617;*CWE-20;BEST CVSS score: '4.4';DESCR 'An unknown typed extent value in on disk freevxfs metadata reaches the default case in vxfs_bmap_typed and executes BUG when block mapping is requested through FIBMAP. The demonstrated primitive is an intentional kernel assertion rather than UAF or out of bounds memory access, so the supported impact is availability loss through an oops or kernel panic. For the CVSS the PR:H value is selected because mounting an attacker controlled filesystem normally requires CAP_SYS_ADMIN and FIBMAP is normally restricted by CAP_SYS_RAWIO. The issue is locally reachable and no direct network trigger or concrete confidentiality or integrity primitive is established. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.4 and the production ActionableScore returned 0 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE to LOW because the ActionableScore threshold rule was applied. final reconciliation stage LOW to LOW because the cross model evidence reconciliation rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS and DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 and V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED. The independent weaker Aegis shadow evaluated CVSS 4.4 and ActionableScore 0 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0)	MAYBE	DANGER DISK SIMPLEFIX LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=0
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=YES
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
RequiresHostUID0=NO
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

1. ActionableScore

* Raw base score: -1.
* Conservative score: 0, applying the score-range floor.
* Raw paranoid score: -1.
* Paranoid score: 0, applying the score-range floor.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 Reliable kernel crash/strong DoS: an unsupported on-disk typed-extent value reaches an unconditional `BUG()`.
* -2 Proven host-admin-equivalent prerequisites: preparing/mounting attacker-controlled FreeVxFS storage normally requires `CAP_SYS_ADMIN`, while `FIBMAP` requires `CAP_SYS_RAWIO`.
* No separate availability point: it would duplicate the same BUG/Oops/panic consequence.
* No memory-corruption, UAF, OOB access, authorization bypass, confidentiality, or integrity signal is shown.
* B5-R does not apply: there is no heap OOB write, retry accumulation, or later consumption of corrupted structured state.
* No Important-preserving trust-boundary primitive is present.

3. Reachability analysis

The malformed extent is attacker-influenced through filesystem media, and `ioctl(FIBMAP)` supplies the demonstrated mapping request. The complete trigger nevertheless requires both mounting suitable storage and invoking a capability-restricted ioctl, supporting effective host-administrator privilege. Numeric UID 0 is not intrinsically required because capabilities, rather than UID, govern these operations. The evidence does not establish that the complete chain works using attacker-obtainable user-namespace capabilities, so namespace scope remains unknown. No race, special hardware, or remote path is involved.

4. Primitive and severity reading

The exact primitive is deliberate assertion failure on an invalid typed-extent discriminator. It is Class C crash/DoS behavior, not corruption of active state. The fix replaces `BUG()` with a warning and returns the existing failure sentinel, which becomes `-EIO`. A kernel Oops or panic is supported; useful post-crash leverage is not. Important candidacy and mandatory review are therefore unwarranted, and automatic downgrade is allowed.

5. One-sentence report phrase

Malformed FreeVxFS metadata can make a privileged FIBMAP operation execute `BUG()`, causing an Oops or panic without a demonstrated memory-corruption or authorization primitive.

6. Manual review advice

NO MANUAL CHECK NEEDED

The patch and call path establish only a privilege-gated assertion-based availability issue.

7. Call-site confidence

Call-site confidence: high

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: freevxfs: don't BUG() on unknown typed-extent type [ Upstream
Commit: fe40a19d571cbb584eea46038ee919d8712b2d2c
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fe40a19d571cbb584eea46038ee919d8712b2d2c

Changed files:
  fs/freevxfs/vxfs_bmap.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fe40a19d571cbb584eea46038ee919d8712b2d2c

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-98872 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98872

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: Not available
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.4

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 0

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).