Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-68368: usb: gadget: f_ncm: validate datagram bounds in ncm_unwrap_ntb()

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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 1febec7e47cdcd01f43fb0211094e3010474666e, 35d15bbaec0557330e774ec31412ef508de6e0e0, 4.10; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1febec7e47cdcd01f43fb0211094e3010474666e, 35d15bbaec0557330e774ec31412ef508de6e0e0, 4.10; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 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: usb: gadget: f_ncm: validate datagram bounds in ncm_unwrap_ntb() When unpacking host-supplied NTBs, ncm_unwrap_ntb() checks datagram length against frame_max but does not verify that the datagram fits within the declared block length. Additionally, when decoding multiple NTBs from a single socket buffer, subsequent block lengths are not checked against the actual remaining buffer data. With these checks missing, a malicious USB host can specify datagram offsets and lengths that point beyond the block, or supply secondary NTB headers declaring lengths larger than the buffer. skb_put_data() then copies adjacent kernel memory from skb_shared_info into the network skb. Fix this by verifying that sufficient buffer space remains for the NTB header before parsing, handling zero-length block declarations, ensuring that block lengths never exceed the remaining buffer space, and verifying that each datagram payload stays strictly within the block boundary.

—No exploit Fix available
Published
Aug 10, 2026
Updated
Aug 19, 2026
EPSS
0.2% · 12th 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.2%

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-2026-68368

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

    • f7e0611e207d8908c4f2858e244370529a76dbf7, b88ad6e714284b33a47834f5f2a294c2b37c66aa, 471b23586387a32857778c511be60ab31c98dcfd, 4f529c4d1e436230d3af7c09a3239677a14d2b46, ae6a5394d9fbe118bc95cfe376d6a9d91d7547e8, 5bdf93a2f5459f944b416b188178ca4a92fd206f, ff3ba016263ee93a1c6209bf5ab1599de7ab1512, e7ca00f35d8a17af1ae19d529193ebc21bfda164, 5.9affected
    • 2b74b0a04d3e9f9f08ff026e5663dce88ff94e52 and later · before 35d15bbaec0557330e774ec31412ef508de6e0e0affected · git
    • 2b74b0a04d3e9f9f08ff026e5663dce88ff94e52 and later · before 6b2be489eaa6293e60549005d91f15ceb150510faffected · git
    • 2b74b0a04d3e9f9f08ff026e5663dce88ff94e52 and later · before f87ed889f0f7417b8938c98d8833f559b755373caffected · git
    • 2b74b0a04d3e9f9f08ff026e5663dce88ff94e52 and later · before e07751d0527ccc2a1c32eb0b0b7da3b4b9b5381faffected · git
    • 2b74b0a04d3e9f9f08ff026e5663dce88ff94e52 and later · before fff1059d139ef798bab917990524faaf25854ca8affected · git
    • 2b74b0a04d3e9f9f08ff026e5663dce88ff94e52 and later · before 40c706a0224bde194667e3378c689b542fec4b44affected · git
    • 2b74b0a04d3e9f9f08ff026e5663dce88ff94e52 and later · before 41fd5f2fb0027d3773ae949e3247c2e0a2a7fe5caffected · git
    • 2b74b0a04d3e9f9f08ff026e5663dce88ff94e52 and later · before 1febec7e47cdcd01f43fb0211094e3010474666eaffected · git
    • 4.9.235 and later · before 4.10affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.101-1~deb12u16.12.101-1~deb12u1
Debian:13linuxbefore 6.12.101-16.12.101-1
Debian:14linuxbefore 7.1.6-17.1.6-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-2026-68366Aug 10, 2026 · usb: gadget: uvc: clamp SEND_RESPONSE length to the response buffer
    0Monitor
  • ← EarlierCVE-2026-68367Aug 10, 2026 · usb: gadget: f_tcm: synchronize delayed set_alt with teardown
    0Monitor
  • Later →CVE-2026-68369Aug 10, 2026 · usb: gadget: printer: fix infinite loop in printer_read()
    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 Linux1febec7e47cdcd01f43fb0211094e3010474666eVendor (CNA)
Linux Linux35d15bbaec0557330e774ec31412ef508de6e0e0Vendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux40c706a0224bde194667e3378c689b542fec4b44Vendor (CNA)
Linux Linux41fd5f2fb0027d3773ae949e3247c2e0a2a7fe5cVendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux5.9Vendor (CNA)
Linux Linux6b2be489eaa6293e60549005d91f15ceb150510fVendor (CNA)
Linux Linuxe07751d0527ccc2a1c32eb0b0b7da3b4b9b5381fVendor (CNA)
Linux Linuxf87ed889f0f7417b8938c98d8833f559b755373cVendor (CNA)
Linux Linuxfff1059d139ef798bab917990524faaf25854ca8Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.150.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.101-1~deb12u1 · 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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

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