CVE-2022-49522: mmc: jz4740: Apply DMA engine limits to maximum segment size
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.26% (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 353298cadbd4c7d8e8a16d6000066414694933c3, 7923f95997a79cef2ad161a2facae64c25a0bca0, 807f90f1960a59dc557542b818c484a8db9ac978.
Low priority for now. Upgrade to Linux Linux 353298cadbd4c7d8e8a16d6000066414694933c3, 7923f95997a79cef2ad161a2facae64c25a0bca0, 807f90f1960a59dc557542b818c484a8db9ac978 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: mmc: jz4740: Apply DMA engine limits to maximum segment size Do what is done in other DMA-enabled MMC host drivers (cf. host/mmci.c) and limit the maximum segment size based on the DMA engine's capabilities. This is needed to avoid warnings like the following with CONFIG_DMA_API_DEBUG=y. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 21 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x2f4/0x39c DMA-API: jz4780-dma 13420000.dma-controller: mapping sg segment longer than device claims to support [len=98304] [max=65536] CPU: 0 PID: 21 Comm: kworker/0:1H Not tainted 5.18.0-rc1 #19 Workqueue: kblockd blk_mq_run_work_fn Stack : 81575aec 00000004 80620000 80620000 80620000 805e7358 00000009 801537ac 814c832c 806276e3 806e34b4 80620000 81575aec 00000001 81575ab8 09291444 00000000 00000000 805e7358 81575958 ffffffea 8157596c 00000000 636f6c62 6220646b 80387a70 0000000f 6d5f6b6c 80620000 00000000 81575ba4 00000009 805e170c 80896640 00000001 00010000 00000000 00000000 00006098 806e0000 ... Call Trace: [<80107670>] show_stack+0x84/0x120 [<80528cd8>] __warn+0xb8/0xec [<80528d78>] warn_slowpath_fmt+0x6c/0xb8 [<8016f1d4>] debug_dma_map_sg+0x2f4/0x39c [<80169d4c>] __dma_map_sg_attrs+0xf0/0x118 [<8016a27c>] dma_map_sg_attrs+0x14/0x28 [<804f66b4>] jz4740_mmc_prepare_dma_data+0x74/0xa4 [<804f6714>] jz4740_mmc_pre_request+0x30/0x54 [<804f4ff4>] mmc_blk_mq_issue_rq+0x6e0/0x7bc [<804f5590>] mmc_mq_queue_rq+0x220/0x2d4 [<8038b2c0>] blk_mq_dispatch_rq_list+0x480/0x664 [<80391040>] blk_mq_do_dispatch_sched+0x2dc/0x370 [<80391468>] __blk_mq_sched_dispatch_requests+0xec/0x164 [<80391540>] blk_mq_sched_dispatch_requests+0x44/0x94 [<80387900>] __blk_mq_run_hw_queue+0xb0/0xcc [<80134c14>] process_one_work+0x1b8/0x264 [<80134ff8>] worker_thread+0x2ec/0x3b8 [<8013b13c>] kthread+0x104/0x10c [<80101dcc>] ret_from_kernel_thread+0x14/0x1c ---[ end trace 0000000000000000 ]---
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
Report tools
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%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.4.198
- linux linux kernel5.5 and later · before 5.10.121
- linux linux kernel5.11 and later · before 5.15.46
- linux linux kernel5.16 and later · before 5.17.14
- linux linux kernel5.18 and later · before 5.18.3
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.18affected
- 7ca27a6f80a4042666a28977ff8ee3aa527c6cd4 and later · before 7923f95997a79cef2ad161a2facae64c25a0bca0affected · git
- 7ca27a6f80a4042666a28977ff8ee3aa527c6cd4 and later · before 90281cadf5077f2d2bec8b08c2ead1f8cd12660eaffected · git
- 7ca27a6f80a4042666a28977ff8ee3aa527c6cd4 and later · before 353298cadbd4c7d8e8a16d6000066414694933c3affected · git
- 7ca27a6f80a4042666a28977ff8ee3aa527c6cd4 and later · before 807f90f1960a59dc557542b818c484a8db9ac978affected · git
- 7ca27a6f80a4042666a28977ff8ee3aa527c6cd4 and later · before a828920b9ec0d89d3011198d482b7fe224d2de19affected · git
- 7ca27a6f80a4042666a28977ff8ee3aa527c6cd4 and later · before afadb04f1d6e74b18a253403f5274cde5e3fd7bdaffected · git
- before 3.18not affected · semver
- 5.4.198 and later · up to and including 5.4.*not affected · semver
- 5.10.121 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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.18.5-1 | 5.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49520Feb 26, 2025 · arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscall22Monitor
- ← EarlierCVE-2022-49521Feb 26, 2025 · scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()22Monitor
- Later →CVE-2022-49523Feb 26, 2025 · ath11k: disable spectral scan during spectral deinit22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 353298cadbd4c7d8e8a16d6000066414694933c3 | Vendor (CNA) |
| Linux Linux | 7923f95997a79cef2ad161a2facae64c25a0bca0 | Vendor (CNA) |
| Linux Linux | 807f90f1960a59dc557542b818c484a8db9ac978 | Vendor (CNA) |
| Linux Linux | 90281cadf5077f2d2bec8b08c2ead1f8cd12660e | Vendor (CNA) |
| Linux Linux | a828920b9ec0d89d3011198d482b7fe224d2de19 | Vendor (CNA) |
| Linux Linux | afadb04f1d6e74b18a253403f5274cde5e3fd7bd | Vendor (CNA) |
| debian:linux | 5.18.5-1 · Debian:12 | Package 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 researchersFinders, 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
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)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/7923f95997a79cef2ad161a2facae64c25a0bca0
- git.kernel.org/stable/c/807f90f1960a59dc557542b818c484a8db9ac978
- git.kernel.org/stable/c/90281cadf5077f2d2bec8b08c2ead1f8cd12660e
- git.kernel.org/stable/c/a828920b9ec0d89d3011198d482b7fe224d2de19
- git.kernel.org/stable/c/afadb04f1d6e74b18a253403f5274cde5e3fd7bd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.