Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68777: Input: ti_am335x_tsc - fix off-by-one error in wire_order validation

—No exploit Fix available

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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 08c0b561823a7026364efb38ed7f4a3af48ccfcd, 136abe173a3cc2951d70c6e51fe7abdbadbb204b, 248d3a73a0167dce15ba100477c3e778c4787178; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 08c0b561823a7026364efb38ed7f4a3af48ccfcd, 136abe173a3cc2951d70c6e51fe7abdbadbb204b, 248d3a73a0167dce15ba100477c3e778c4787178; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.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: Input: ti_am335x_tsc - fix off-by-one error in wire_order validation The current validation 'wire_order[i] > ARRAY_SIZE(config_pins)' allows wire_order[i] to equal ARRAY_SIZE(config_pins), which causes out-of-bounds access when used as index in 'config_pins[wire_order[i]]'. Since config_pins has 4 elements (indices 0-3), the valid range for wire_order should be 0-3. Fix the off-by-one error by using >= instead of > in the validation check.

Published
Jan 13, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 10th 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-2025-68777

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

    • 3.11affected
    • bb76dc09ddfc135c6c5e8eb7d3c583bfa8bdd439 and later · before a7ff2360431561b56f559d3a628d1f096048d178affected · git
    • bb76dc09ddfc135c6c5e8eb7d3c583bfa8bdd439 and later · before 136abe173a3cc2951d70c6e51fe7abdbadbb204baffected · git
    • bb76dc09ddfc135c6c5e8eb7d3c583bfa8bdd439 and later · before 08c0b561823a7026364efb38ed7f4a3af48ccfcdaffected · git
    • bb76dc09ddfc135c6c5e8eb7d3c583bfa8bdd439 and later · before bf95ec55805828c4f2b5241fb6b0c12388548570affected · git
    • bb76dc09ddfc135c6c5e8eb7d3c583bfa8bdd439 and later · before 84e4d3543168912549271b34261f5e0f94952d6eaffected · git
    • bb76dc09ddfc135c6c5e8eb7d3c583bfa8bdd439 and later · before 40e3042de43ffa0017a8460ff9b4cad7b8c7cb96affected · git
    • bb76dc09ddfc135c6c5e8eb7d3c583bfa8bdd439 and later · before 248d3a73a0167dce15ba100477c3e778c4787178affected · git
    • before 3.11not affected · semver
    • 5.10.248 and later · up to and including 5.10.*not 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.69-16.12.69-1
Debian:14linuxbefore 6.18.3-16.18.3-1

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-68772Jan 13, 2026 · f2fs: fix to avoid updating compression context during writeback
    0Monitor
  • ← EarlierCVE-2025-68774Jan 13, 2026 · hfsplus: fix missing hfs_bnode_get() in __hfs_bnode_create
    30Monitor
  • Later →CVE-2025-68778Jan 13, 2026 · btrfs: don't log conflicting inode if it's a dir moved in the current transaction
    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 Linux08c0b561823a7026364efb38ed7f4a3af48ccfcdVendor (CNA)
Linux Linux136abe173a3cc2951d70c6e51fe7abdbadbb204bVendor (CNA)
Linux Linux248d3a73a0167dce15ba100477c3e778c4787178Vendor (CNA)
Linux Linux40e3042de43ffa0017a8460ff9b4cad7b8c7cb96Vendor (CNA)
Linux Linux84e4d3543168912549271b34261f5e0f94952d6eVendor (CNA)
Linux Linuxa7ff2360431561b56f559d3a628d1f096048d178Vendor (CNA)
Linux Linuxbf95ec55805828c4f2b5241fb6b0c12388548570Vendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

References

All records