In the Linux kernel, the following vulnerability has been resolved:
uacce: fix isolate sysfs check condition
uacce supports the device isolation feature. If the driver
implements the isolate_err_threshold_read and
isolate_err_threshold_write callback functions, uacce will create
sysfs files now. Users can read and configure the isolation policy
through sysfs. Currently, sysfs files are created as long as either
isolate_err_threshold_read or isolate_err_threshold_write callback
functions are present.
However, accessing a non-existent callback function may cause the
system to crash. Therefore, intercept the creation of sysfs if
neither read nor write exists; create sysfs if either is supported,
but intercept unsupported operations at the call site.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can let an unsafe sysfs access path crash a system when uacce device isolation support is only partially implemented. The business impact is availability, not confirmed data theft or remote compromise, based on the supplied sources.
Executive priority
Treat as a targeted availability risk. Patch in normal kernel maintenance, faster for shared, multi-user, or accelerator-heavy systems where a crash would disrupt production workloads.
Technical view
In uacce, sysfs isolation files could be created when either read or write callback existed. The fix prevents unsupported operations from calling a missing callback. The source says accessing a non-existent callback may crash the system.
Likely exposure
Exposure appears limited to Linux systems using uacce device isolation sysfs support, likely accelerator-related deployments. The bundle does not prove general Linux exposure or specify exact affected distributions.
Exploitation context
The bundle provides no CVSS, CWE, KEV listing, or active exploitation evidence. It describes a crash condition from accessing unsupported sysfs operations; required privileges and practical exploitability are not specified.
Researcher notes
The public bundle is sparse. It supports a missing-callback crash in uacce sysfs isolation handling, but does not define privileges, attack surface beyond sysfs, CVSS, affected distro packages, or exploit status.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
Check Linux distribution advisories for fixed package versions.
Prioritize systems using uacce-capable accelerator hardware or drivers.
If no update is available, follow vendor guidance for temporary controls.
Validation and detection
Inventory Linux kernel versions against distribution security advisories.
Identify systems using uacce or accelerator drivers with isolation sysfs support.
Confirm deployed kernels include one of the referenced stable fixes or vendor backports.
Review local access assumptions for users able to interact with relevant sysfs entries.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23094 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 4, 2026, 16:08 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.