LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23349: HID: pidff: Fix condition effect bit clearing

In the Linux kernel, the following vulnerability has been resolved: HID: pidff: Fix condition effect bit clearing As reported by MPDarkGuy on discord, NULL pointer dereferences were happening because not all the conditional effects bits were cleared. Properly clear all conditional effect bits from ffbit

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23349 is a Linux kernel flaw in HID force-feedback handling. The reported failure is a NULL pointer dereference caused by incomplete clearing of condition-effect bits. In business terms, this is primarily an availability and stability concern for systems running affected kernels, not a confirmed data-theft issue from the provided sources.

Executive priority

Handle through normal kernel patch management unless affected systems are stability-critical or use relevant HID force-feedback hardware. There is no source-supported active exploitation signal, but kernel NULL dereference bugs can still create operational disruption.

Technical view

The Linux kernel pidff HID code failed to clear all conditional effect bits from ffbit. The CVE record says this caused NULL pointer dereferences. The issue is marked resolved in Linux stable commits, but the provided bundle has no CVSS, CWE, or detailed exploit preconditions.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel builds with the vulnerable HID pidff code path. Systems using HID force-feedback devices may be more relevant. Exact exposure depends on distribution backports and kernel package versions, which are not fully resolved by the source bundle.

Exploitation context

The bundle states KEV is false and provides no cited evidence of active exploitation. The report source mentioned is a Discord report of NULL pointer dereferences, not a public exploitation campaign. Treat exploitability details as incomplete.

Researcher notes

The public record is sparse: no CVSS, CWE, detailed threat model, or proof-of-concept is included. Analysis should focus on commit review, distro backport mapping, and crash telemetry rather than assuming remote reachability or privilege impact.

Mitigation direction

  • Identify Linux kernel versions and distribution package levels across managed systems.
  • Prioritize updates that include the referenced Linux stable fixes.
  • Check Linux distribution advisories for backported fixed package versions.
  • If patching is delayed, review exposure to HID force-feedback device usage.

Validation and detection

  • Confirm whether fleet kernels map to the affected version data in the CVE record.
  • Verify installed kernels include one of the referenced stable commits or distributor backports.
  • Review crash logs for NULL pointer dereferences involving HID pidff paths.
  • Track vendor advisories until affected and fixed package ranges are explicit.
Prepared
Confidence
medium
Sources
5

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-23349 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7f3d7bc0df4bdc23d31cf0f90b6e20c45129465e, 7f3d7bc0df4bdc23d31cf0f90b6e20c45129465e, 7f3d7bc0df4bdc23d31cf0f90b6e20c45129465eunaffected
LinuxLinux6.18, 0, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.