Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54255: sh: dma: Fix DMA channel offset calculation

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 196f6c71905aa384c0177acf194a1144d480333b, 479380acfa63247b5ac62476138f847aefc62692, 4989627157735c1f1619f08e5bc1592418e7c878.

Low priority for now. Upgrade to Linux Linux 196f6c71905aa384c0177acf194a1144d480333b, 479380acfa63247b5ac62476138f847aefc62692, 4989627157735c1f1619f08e5bc1592418e7c878 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: sh: dma: Fix DMA channel offset calculation Various SoCs of the SH3, SH4 and SH4A family, which use this driver, feature a differing number of DMA channels, which can be distributed between up to two DMAC modules. The existing implementation fails to correctly accommodate for all those variations, resulting in wrong channel offset calculations and leading to kernel panics. Rewrite dma_base_addr() in order to properly calculate channel offsets in a DMAC module. Fix dmaor_read_reg() and dmaor_write_reg(), so that the correct DMAC module base is selected for the DMAOR register.

—No exploit Fix available
Published
Dec 30, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 11th 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-2023-54255

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

    • 3.5affected
    • 7f47c7189b3e8f19a589f77a3ad169d7b691b582 and later · before bca700b48c72f4ffeee977a2ed0eb4a6b4b7b8adaffected · git
    • 7f47c7189b3e8f19a589f77a3ad169d7b691b582 and later · before 479380acfa63247b5ac62476138f847aefc62692affected · git
    • 7f47c7189b3e8f19a589f77a3ad169d7b691b582 and later · before 4989627157735c1f1619f08e5bc1592418e7c878affected · git
    • 7f47c7189b3e8f19a589f77a3ad169d7b691b582 and later · before d1c946552af299f4fa85bf7da15e328123771128affected · git
    • 7f47c7189b3e8f19a589f77a3ad169d7b691b582 and later · before 196f6c71905aa384c0177acf194a1144d480333baffected · git
    • 7f47c7189b3e8f19a589f77a3ad169d7b691b582 and later · before 8fb11fa4805699c6b73a9c8a9d45807f9874abe3affected · git
    • 7f47c7189b3e8f19a589f77a3ad169d7b691b582 and later · before e9e33faea104381bac80ac79328f0540fc2969f2affected · git
    • 7f47c7189b3e8f19a589f77a3ad169d7b691b582 and later · before e82e47584847129a20b8c9f4a1dcde09374fb0e0affected · git
    • before 3.5not 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.52-16.1.52-1
Debian:13linuxbefore 6.4.4-16.4.4-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-2023-54252Dec 30, 2025 · platform/x86: think-lmi: Fix memory leaks when parsing ThinkStation WMI strings
    0Monitor
  • ← EarlierCVE-2023-54253Dec 30, 2025 · btrfs: set page extent mapped after read_folio in relocate_one_page
    0Monitor
  • Later →CVE-2023-54257Dec 30, 2025 · net: macb: fix a memory corruption in extended buffer descriptor mode
    39Monitor

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 Linux196f6c71905aa384c0177acf194a1144d480333bVendor (CNA)
Linux Linux479380acfa63247b5ac62476138f847aefc62692Vendor (CNA)
Linux Linux4989627157735c1f1619f08e5bc1592418e7c878Vendor (CNA)
Linux Linux8fb11fa4805699c6b73a9c8a9d45807f9874abe3Vendor (CNA)
Linux Linuxbca700b48c72f4ffeee977a2ed0eb4a6b4b7b8adVendor (CNA)
Linux Linuxd1c946552af299f4fa85bf7da15e328123771128Vendor (CNA)
Linux Linuxe82e47584847129a20b8c9f4a1dcde09374fb0e0Vendor (CNA)
Linux Linuxe9e33faea104381bac80ac79328f0540fc2969f2Vendor (CNA)
debian:linux6.1.52-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