Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68758: backlight: led-bl: Add devlink to supplier LEDs

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 08c9dc6b0f2c68e5e7c374ac4499e321e435d46c, 0e63ea4378489e09eb5e920c8a50c10caacf563a, 30cbe4b642745a9488a0f0d78be43afe69d7555c.

Low priority for now. Upgrade to Linux Linux 08c9dc6b0f2c68e5e7c374ac4499e321e435d46c, 0e63ea4378489e09eb5e920c8a50c10caacf563a, 30cbe4b642745a9488a0f0d78be43afe69d7555c or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: backlight: led-bl: Add devlink to supplier LEDs LED Backlight is a consumer of one or multiple LED class devices, but devlink is currently unable to create correct supplier-producer links when the supplier is a class device. It creates instead a link where the supplier is the parent of the expected device. One consequence is that removal order is not correctly enforced. Issues happen for example with the following sections in a device tree overlay: // An LED driver chip pca9632@62 { compatible = "nxp,pca9632"; reg = <0x62>; // ... addon_led_pwm: led-pwm@3 { reg = <3>; label = "addon:led:pwm"; }; }; backlight-addon { compatible = "led-backlight"; leds = <&addon_led_pwm>; brightness-levels = <255>; default-brightness-level = <255>; }; In this example, the devlink should be created between the backlight-addon (consumer) and the pca9632@62 (supplier). Instead it is created between the backlight-addon (consumer) and the parent of the pca9632@62, which is typically the I2C bus adapter. On removal of the above overlay, the LED driver can be removed before the backlight device, resulting in: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 ... Call trace: led_put+0xe0/0x140 devm_led_release+0x6c/0x98 Another way to reproduce the bug without any device tree overlays is unbinding the LED class device (pca9632@62) before unbinding the consumer (backlight-addon): echo 11-0062 >/sys/bus/i2c/drivers/leds-pca963x/unbind echo ...backlight-dock >/sys/bus/platform/drivers/led-backlight/unbind Fix by adding a devlink between the consuming led-backlight device and the supplying LED device, as other drivers and subsystems do as well.

—No exploit Fix available
Published
Jan 5, 2026
Updated
Oct 14, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68758

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.6affected
    • ae232e45acf9621f2c96b41ca3af006ac7552c33 and later · before 64739adf3eef063b8e2c72b7e919eac8c6480bf0affected · git
    • ae232e45acf9621f2c96b41ca3af006ac7552c33 and later · before cd01a24b3e52d6777b49c917d841f125fe9eebd0affected · git
    • ae232e45acf9621f2c96b41ca3af006ac7552c33 and later · before e06df738a9ad8417f1c4c7cd6992cda320e9e7caaffected · git
    • ae232e45acf9621f2c96b41ca3af006ac7552c33 and later · before 30cbe4b642745a9488a0f0d78be43afe69d7555caffected · git
    • ae232e45acf9621f2c96b41ca3af006ac7552c33 and later · before 0e63ea4378489e09eb5e920c8a50c10caacf563aaffected · git
    • ae232e45acf9621f2c96b41ca3af006ac7552c33 and later · before 60a24070392ec726ccfe6ad1ca7b0381c8d8f7c9affected · git
    • ae232e45acf9621f2c96b41ca3af006ac7552c33 and later · before 08c9dc6b0f2c68e5e7c374ac4499e321e435d46caffected · git
    • ae232e45acf9621f2c96b41ca3af006ac7552c33 and later · before 9341d6698f4cfdfc374fb6944158d111ebe16a9daffected · git
    • before 5.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.13-16.17.13-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68755Jan 5, 2026 · staging: most: remove broken i2c driver
    0Monitor
  • ← EarlierCVE-2025-68756Jan 5, 2026 · block: Use RCU in blk_mq_[un]quiesce_tagset() instead of set->tag_list_lock
    0Monitor
  • Later →CVE-2025-68759Jan 5, 2026 · wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux08c9dc6b0f2c68e5e7c374ac4499e321e435d46cVendor (CNA)
Linux Linux0e63ea4378489e09eb5e920c8a50c10caacf563aVendor (CNA)
Linux Linux30cbe4b642745a9488a0f0d78be43afe69d7555cVendor (CNA)
Linux Linux60a24070392ec726ccfe6ad1ca7b0381c8d8f7c9Vendor (CNA)
Linux Linux64739adf3eef063b8e2c72b7e919eac8c6480bf0Vendor (CNA)
Linux Linux9341d6698f4cfdfc374fb6944158d111ebe16a9dVendor (CNA)
Linux Linuxcd01a24b3e52d6777b49c917d841f125fe9eebd0Vendor (CNA)
Linux Linuxe06df738a9ad8417f1c4c7cd6992cda320e9e7caVendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records