Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26600: phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP

Noroxi assessment

Priority: Monitor (action score 22/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.29% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0430bfcd46657d9116a26cd377f112cbc40826a4, 14ef61594a5a286ae0d493b8acbf9eac46fd04c4, 396e17af6761b3cc9e6e4ca94b4de7f642bfece1.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0430bfcd46657d9116a26cd377f112cbc40826a4, 14ef61594a5a286ae0d493b8acbf9eac46fd04c4, 396e17af6761b3cc9e6e4ca94b4de7f642bfece1 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: phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP If the external phy working together with phy-omap-usb2 does not implement send_srp(), we may still attempt to call it. This can happen on an idle Ethernet gadget triggering a wakeup for example: configfs-gadget.g1 gadget.0: ECM Suspend configfs-gadget.g1 gadget.0: Port suspended. Triggering wakeup ... Unable to handle kernel NULL pointer dereference at virtual address 00000000 when execute ... PC is at 0x0 LR is at musb_gadget_wakeup+0x1d4/0x254 [musb_hdrc] ... musb_gadget_wakeup [musb_hdrc] from usb_gadget_wakeup+0x1c/0x3c [udc_core] usb_gadget_wakeup [udc_core] from eth_start_xmit+0x3b0/0x3d4 [u_ether] eth_start_xmit [u_ether] from dev_hard_start_xmit+0x94/0x24c dev_hard_start_xmit from sch_direct_xmit+0x104/0x2e4 sch_direct_xmit from __dev_queue_xmit+0x334/0xd88 __dev_queue_xmit from arp_solicit+0xf0/0x268 arp_solicit from neigh_probe+0x54/0x7c neigh_probe from __neigh_event_send+0x22c/0x47c __neigh_event_send from neigh_resolve_output+0x14c/0x1c0 neigh_resolve_output from ip_finish_output2+0x1c8/0x628 ip_finish_output2 from ip_send_skb+0x40/0xd8 ip_send_skb from udp_send_skb+0x124/0x340 udp_send_skb from udp_sendmsg+0x780/0x984 udp_sendmsg from __sys_sendto+0xd8/0x158 __sys_sendto from ret_fast_syscall+0x0/0x58 Let's fix the issue by checking for send_srp() and set_vbus() before calling them. For USB peripheral only cases these both could be NULL.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 22th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-2024-26600

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.7.0 and later · before 4.19.307
  • linux linux kernel4.20.0 and later · before 5.4.269
  • linux linux kernel5.5.0 and later · before 5.10.210
  • linux linux kernel5.11.0 and later · before 5.15.149
  • linux linux kernel5.16.0 and later · before 6.1.78
  • linux linux kernel6.2.0 and later · before 6.6.17
  • linux linux kernel6.7.0 and later · before 6.7.5

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

    • 3.7affected
    • 657b306a7bdfca4ae1514b533a0e7c3c6d26dbc6 and later · before 486218c11e8d1c8f515a3bdd70d62203609d4b6baffected · git
    • 657b306a7bdfca4ae1514b533a0e7c3c6d26dbc6 and later · before 8398d8d735ee93a04fb9e9f490e8cacd737e3bf5affected · git
    • 657b306a7bdfca4ae1514b533a0e7c3c6d26dbc6 and later · before be3b82e4871ba00e9b5d0ede92d396d579d7b3b3affected · git
    • 657b306a7bdfca4ae1514b533a0e7c3c6d26dbc6 and later · before 8cc889b9dea0579726be9520fcc766077890b462affected · git
    • 657b306a7bdfca4ae1514b533a0e7c3c6d26dbc6 and later · before 0430bfcd46657d9116a26cd377f112cbc40826a4affected · git
    • 657b306a7bdfca4ae1514b533a0e7c3c6d26dbc6 and later · before 14ef61594a5a286ae0d493b8acbf9eac46fd04c4affected · git
    • 657b306a7bdfca4ae1514b533a0e7c3c6d26dbc6 and later · before 396e17af6761b3cc9e6e4ca94b4de7f642bfece1affected · git
    • 657b306a7bdfca4ae1514b533a0e7c3c6d26dbc6 and later · before 7104ba0f1958adb250319e68a15eff89ec4fd36daffected · git
    • before 3.7not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.31.1.el9_47.3.0-427.31.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-52472Feb 26, 2024 · crypto: rsa - add a check for allocation failure
    22Monitor
  • ← EarlierCVE-2023-52473Feb 26, 2024 · thermal: core: Fix NULL pointer dereference in zone registration error path
    22Monitor
  • Later →CVE-2024-26601Feb 26, 2024 · ext4: regenerate buddy after block freeing failed if under fc replay
    22Monitor

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 Linux0430bfcd46657d9116a26cd377f112cbc40826a4Vendor (CNA)
Linux Linux14ef61594a5a286ae0d493b8acbf9eac46fd04c4Vendor (CNA)
Linux Linux396e17af6761b3cc9e6e4ca94b4de7f642bfece1Vendor (CNA)
Linux Linux486218c11e8d1c8f515a3bdd70d62203609d4b6bVendor (CNA)
Linux Linux7104ba0f1958adb250319e68a15eff89ec4fd36dVendor (CNA)
Linux Linux8398d8d735ee93a04fb9e9f490e8cacd737e3bf5Vendor (CNA)
Linux Linux8cc889b9dea0579726be9520fcc766077890b462Vendor (CNA)
Linux Linuxbe3b82e4871ba00e9b5d0ede92d396d579d7b3b3Vendor (CNA)
almalinux:bpftool7.3.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+4

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

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 (9 more)

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

All records