Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93051misc: ad525x_dpot: use driver core groups for sysfs files

Description

In the Linux kernel, the following vulnerability has been resolved: misc: ad525x_dpot: use driver core groups for sysfs files ad_dpot_probe() creates per-RDAC sysfs files manually and then optionally creates the command sysfs group. This leaves probe responsible for rolling back partial sysfs state and makes remove responsible for matching every file that probe created. Move the device attributes into driver core dev_groups for the I2C and SPI drivers and use an is_visible() callback to expose only the attributes supported by the probed device. With this shape, the driver core creates the sysfs files only after probe succeeds and removes them before the remove callback frees the driver data.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 4eb174bee6f8623fed1af0072f1bebfc3b513a52 – < 1d43cef1d4ff258dee3020cc29f29fd6becfd8b9
    • affected 4eb174bee6f8623fed1af0072f1bebfc3b513a52 – < ddbd794e543e5f917d191f8259ce40b79c52d105
    • affected 4eb174bee6f8623fed1af0072f1bebfc3b513a52 – < aa3ace3f6c66811001ffa63a53fbb01ed8109312
    • affected 4eb174bee6f8623fed1af0072f1bebfc3b513a52 – < 0394902df38279da7f880021b2cfc64577a60e42
    • affected 4eb174bee6f8623fed1af0072f1bebfc3b513a52 – < e30f2c23c8d5620f9679e3b6656a6eb7cb1fd38b
    • affected 4eb174bee6f8623fed1af0072f1bebfc3b513a52 – < c7ff7a70f405a3c6fde39ed00a36d9f4fecaf3ab
    • affected 4eb174bee6f8623fed1af0072f1bebfc3b513a52 – < ab2fe43041412d37f88eb368a99f63f98b31d8ea
    • affected 4eb174bee6f8623fed1af0072f1bebfc3b513a52 – < e3a8557e88eb26278eda60bf64f2ef33ce7de8bf
  • Linux · Linux

    • affected 2.6.33
    • unaffected < 2.6.33
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93051 badge
[![CVE-2026-93051](https://cveledger.app/badge/CVE-2026-93051.svg)](https://cveledger.app/cve/CVE-2026-93051)

Record last updated .