LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46097: Input: edt-ft5x06 - fix use-after-free in debugfs teardown

In the Linux kernel, the following vulnerability has been resolved: Input: edt-ft5x06 - fix use-after-free in debugfs teardown The commit 68743c500c6e ("Input: edt-ft5x06 - use per-client debugfs directory") removed the manual debugfs teardown, relying on the I2C core to handle it. However, this creates a window where debugfs files are still accessible after edt_ft5x06_ts_teardown_debugfs() frees tsdata->raw_buffer. To prevent a use-after-free, protect the freeing of raw_buffer with the device mutex and set raw_buffer to NULL. The debugfs read function already checks if raw_buffer is NULL under the same mutex, so this safely avoids the use-after-free.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel use-after-free in the edt-ft5x06 touchscreen driver’s debugfs cleanup path. It appears narrow and device-driver specific, but affected systems should take kernel updates seriously because memory-safety bugs in kernel code can have high impact if reachable.

Executive priority

Treat as a targeted kernel maintenance item, not an internet-wide emergency based on current evidence. Prioritize affected embedded, kiosk, industrial, or touchscreen Linux deployments once vendor patches are available.

Technical view

A prior change removed manual debugfs teardown and relied on I2C core cleanup. That left a window where debugfs files could be read after raw_buffer was freed. The fix protects raw_buffer teardown with the device mutex and sets the pointer to NULL.

Likely exposure

Exposure appears limited to Linux systems using affected kernels with the edt-ft5x06 input driver and its debugfs files reachable. The provided data does not establish exposure for generic Linux servers, containers, or unrelated input devices.

Exploitation context

The bundle does not cite active exploitation, public exploit availability, or CISA KEV listing. Reachability depends on local system configuration and access to the relevant debugfs interface; the sources do not describe remote attack paths.

Researcher notes

The root cause is a teardown race around debugfs lifetime and raw_buffer ownership. Evidence supports the fix mechanism, but not severity, exploitability, or affected distribution package ranges. Validate against exact kernel trees and vendor backports.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Track distribution advisories for affected kernel package versions.
  • Prioritize embedded or touchscreen-enabled Linux systems using edt-ft5x06.
  • Apply normal debugfs access restrictions according to vendor guidance.
  • Avoid relying on version inference without vendor confirmation.

Validation and detection

  • Inventory Linux kernel versions across relevant device fleets.
  • Identify systems loading or building the edt-ft5x06 driver.
  • Confirm whether vendor packages include the referenced stable commits.
  • Check whether debugfs is enabled on candidate systems.
  • Review CVE and vendor advisories for updated severity data.
Prepared
Confidence
medium
Sources
5

Public sources used

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux68743c500c6eafcd0b16dc6067fea5bca0795eef, 68743c500c6eafcd0b16dc6067fea5bca0795eef, 68743c500c6eafcd0b16dc6067fea5bca0795eefunaffected
LinuxLinux6.17, 0, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

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