[CVE-2026-45943][MODERATE REGULAR] erofs: fix inline data read failure for ztailpacking pclusters [ Upstream

[CVE-2026-45943][MODERATE REGULAR] erofs: fix inline data read failure for ztailpacking pclusters [ Upstream

[AL-KERNEL]

CVE: CVE-2026-45943
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: erofs: fix inline data read failure for ztailpacking pclusters [ Upstream
Commit: ad07ea069f924465061cfee40ef2861bb99f4dd8
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ad07ea069f924465061cfee40ef2861bb99f4dd8
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45943
Analysis date: Wed, 27 May 2026 20:11:37 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Borderline Moderate / likely auto-close after lightweight review
Manual review required: NO

Summary:
An EROFS inline-data decompression ordering bug can leave a ztailpacking pcluster in an invalid state and allow a local reader of an affected mounted image to trigger a timing-dependent NULL pointer dereference, causing kernel DoS.

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

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

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: MODERATE REGULAR
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-45943	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'An EROFS NULL pointer dereference can occur when inline data for ztailpacking pclusters is added to I/O chains before the compressed folio is valid. A local user can trigger the vulnerable path by reading data from an affected mounted EROFS image if a fatal signal interrupts read_mapping_folio at the wrong time. For the CVSS the PR:L is used because local user context is needed to issue the read and influence the signal timing, while full administrator privileges are not required once the filesystem is mounted and accessible. The issue is not network reachable. Impact is denial of service via kernel crash. No direct evidence of information disclosure or privilege escalation is indicated by the code path.';NO MANUAL CHECK; ,and ActionableScore result is Borderline Moderate / likely auto-close after lightweight review (with actual score 3) 	MAYBE	OOB NULLPTR DISK INIT LINUS MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	guess

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

ActionableScore=3
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 3
* Final recommended bucket: **Borderline Moderate / likely auto-close after lightweight review**::

## 2. Signal breakdown

* Local unprivileged trigger: +1
  A local user can issue reads against an already mounted affected EROFS filesystem and can influence signal timing for its own process.

* Reliable kernel crash / strong DoS: +1
  The described failure is a NULL pointer dereference in the decompression path and can crash the kernel when the bad state is reached.

* Availability impact realistic: +1
  The demonstrated impact is system availability loss via kernel crash.

* Hard or unreliable race / special timing required: -1
  The commit explicitly says the issue is somewhat hard to reproduce and depends on a fatal signal arriving while read_mapping_folio() is running.

* Important filesystem/storage path: +1 in paranoid scoring only
  This is in a filesystem decompression read path, but it is not metadata corruption, writeback corruption, or page-cache ownership corruption, so I would not count it strongly in the conservative score.

* No generic memory corruption: +0
  The patch supports NULL pointer dereference / invalid state handling, not UAF, double-free, OOB write, heap overwrite, or page-cache corruption.

* No privilege escalation plausible signal: +0
  There is no supported reclaim primitive, controlled overwrite, arbitrary write, or sensitive data exposure path.

## 3. Reachability analysis

The bug is locally reachable when an affected EROFS filesystem with ztailpacking inline data is mounted and readable by the attacker. Triggering requires a specific compressed inline-data layout and a timing condition involving interruption by a fatal signal during read_mapping_folio(). Namespaces do not substantially change the core assessment unless an unprivileged user can arrange mounting of crafted EROFS images through a delegated mount environment. In typical host deployments, creating or mounting the crafted filesystem image requires privilege, but reading an already mounted image may not.

The path is not network reachable. It is not a default packet-processing or remote protocol parser path. Realistic exploitation is DoS-oriented and timing-sensitive.

## 4. Severity interpretation

This behaves like an ordinary Moderate kernel DoS rather than an Important-class vulnerability. The theoretical bug class is invalid state leading to NULL pointer dereference, not demonstrated memory corruption. The realistic impact is kernel crash only. The paranoid score is slightly higher because repeated local attempts against an already mounted affected image may make the timing more practical, but there is still no evidence of confidentiality impact, integrity impact, or privilege escalation.

## 5. One-sentence report phrase

An EROFS inline-data decompression ordering bug can leave a ztailpacking pcluster in an invalid state and allow a local reader of an affected mounted image to trigger a timing-dependent NULL pointer dereference, causing kernel DoS.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be handled as an auto-close or low-priority Moderate unless the environment allows untrusted users to mount crafted EROFS images or the filesystem is widely exposed to untrusted local workloads.

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

Patch: erofs: fix inline data read failure for ztailpacking pclusters [ Upstream
Commit: ad07ea069f924465061cfee40ef2861bb99f4dd8
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ad07ea069f924465061cfee40ef2861bb99f4dd8

Changed files:
  fs/erofs/zdata.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=ad07ea069f924465061cfee40ef2861bb99f4dd8

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

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

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: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

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: 2
  Paranoid ActionableScore: 3

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: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

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).