CVE-2022-49163: media: imx-jpeg: fix a bug of accessing array out of bounds
Noroxi assessment
Priority: Monitor (action score 28/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.27% (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 02f9f97d54ffc85b50ad77f5b1f3c8f69cd17747, 20c8b90430c5d6c4a3936eaa7c35aac670581487, 97558d170a1236280407e8d29a7d095d2c2ed554.
Low priority for now. Upgrade to Linux Linux 02f9f97d54ffc85b50ad77f5b1f3c8f69cd17747, 20c8b90430c5d6c4a3936eaa7c35aac670581487, 97558d170a1236280407e8d29a7d095d2c2ed554 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: media: imx-jpeg: fix a bug of accessing array out of bounds When error occurs in parsing jpeg, the slot isn't acquired yet, it may be the default value MXC_MAX_SLOTS. If the driver access the slot using the incorrect slot number, it will access array out of bounds. The result is the driver will change num_domains, which follows slot_data in struct mxc_jpeg_dev. Then the driver won't detach the pm domain at rmmod, which will lead to kernel panic when trying to insmod again.
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-125
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 7.1
- CNA · Linux
- 7.1
- agree
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 |
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
- 5.13affected
- 2db16c6ed72ce644d5639b3ed15e5817442db4ba and later · before 02f9f97d54ffc85b50ad77f5b1f3c8f69cd17747affected · git
- 2db16c6ed72ce644d5639b3ed15e5817442db4ba and later · before 20c8b90430c5d6c4a3936eaa7c35aac670581487affected · git
- 2db16c6ed72ce644d5639b3ed15e5817442db4ba and later · before e209e6db2e527db6a93b14c2deedf969caca78fcaffected · git
- 2db16c6ed72ce644d5639b3ed15e5817442db4ba and later · before 97558d170a1236280407e8d29a7d095d2c2ed554affected · git
- before 5.13not affected · semver
- 5.15.33 and later · up to and including 5.15.*not affected · semver
- 5.16.19 and later · up to and including 5.16.*not affected · semver
- 5.17.2 and later · up to and including 5.17.*not affected · semver
- 5.18 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.13 and later · before 5.15.33
- linux linux kernel5.16 and later · before 5.16.19
- linux linux kernel5.17 and later · before 5.17.2
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.17.3-1 | 5.17.3-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-49161Feb 26, 2025 · ASoC: mediatek: Fix error handling in mt8183_da7219_max98357_dev_probe22Monitor
- ← EarlierCVE-2022-49162Feb 26, 2025 · video: fbdev: sm712fb: Fix crash in smtcfb_write()22Monitor
- Later →CVE-2022-49164Feb 26, 2025 · powerpc/tm: Fix more userspace r13 corruption22Monitor
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 | 02f9f97d54ffc85b50ad77f5b1f3c8f69cd17747 | Vendor (CNA) |
| Linux Linux | 20c8b90430c5d6c4a3936eaa7c35aac670581487 | Vendor (CNA) |
| Linux Linux | 97558d170a1236280407e8d29a7d095d2c2ed554 | Vendor (CNA) |
| Linux Linux | e209e6db2e527db6a93b14c2deedf969caca78fc | Vendor (CNA) |
| debian:linux | 5.17.3-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- high · data can be read
- 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
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.