Skip to content
Fencer Vulns
medium 4.4

CVE-2024-26747 json

usb: roles: fix NULL pointer issue when put module's reference

published 2024-04-03 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-24009

cvss
4.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

usb: roles: fix NULL pointer issue when put module's reference

In current design, usb role class driver will get usb_role_switch parent's module reference after the user get usb_role_switch device and put the reference after the user put the usb_role_switch device. However, the parent device of usb_role_switch may be removed before the user put the usb_role_switch. If so, then, NULL pointer issue will be met when the user put the parent module's reference.

This will save the module pointer in structure of usb_role_switch. Then, we don't need to find module by iterating long relations.

Patch / fix

  • Linux Linux 4.19, 5.10.211, 5.15.150, 6.1.80, 6.6.19, 6.7.7, 6.8
  • linux Debian 12 6.1.82-1
  • linux Debian 14, Debian 13 6.7.7-1

debian advisories DEBIAN-CVE-2024-26747

  • linux Ubuntu 22.04 LTS 5.15.0-112.122
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1063.69
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1062.70
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1060.66
  • linux-ibm Ubuntu 22.04 LTS 5.15.0-1056.59
  • linux-kvm Ubuntu 22.04 LTS 5.15.0-1060.65
  • linux-azure Ubuntu 22.04 LTS 5.15.0-1066.75
  • linux-gkeop Ubuntu 22.04 LTS 5.15.0-1046.53

ubuntu advisories UBUNTU-CVE-2024-26747

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-syms SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.216.1
  • kernel-source SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.216.1
  • kernel-default SLES for SAP 12 SP5, SLES 12 SP5, SLE Workstation Extension 12 SP5 +2 more 4.12.14-122.216.1
  • kernel-obs-build SLE Software Development Kit 12 SP5 4.12.14-122.216.1
  • kernel-rt SLE Micro 5.5, Real Time Module 15 SP5, openSUSE Leap 15.5 5.14.21-150500.13.52.1
  • kernel-syms-rt Real Time Module 15 SP5, openSUSE Leap 15.5 5.14.21-150500.13.52.1
  • kernel-rt_debug Real Time Module 15 SP5, openSUSE Leap 15.5 5.14.21-150500.13.52.1
  • kernel-source-rt SLE Micro 5.5, Real Time Module 15 SP5, openSUSE Leap 15.5 5.14.21-150500.13.52.1

suse advisories SUSE-SU-2024:1870-1SUSE-SU-2024:1663-1SUSE-SU-2024:1659-1SUSE-SU-2024:1646-1SUSE-SU-2024:1643-1SUSE-SU-2024:1490-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-26747 updated cvss 4.4

kernel: usb: roles: fix NULL pointer issue when put module's reference

  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.