media: atomisp: Add check for rgby_data memory allocation failure
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 02a97d9d7ff605fa4a1f908d1bd3ad8573234b61, 0c24b82bc4d12c6a58ceacbf2598cd4df63abf9a, 0c25ab93f2878cab07d37ca5afd302283201e5af.
Low priority for now. Upgrade to Linux Linux 02a97d9d7ff605fa4a1f908d1bd3ad8573234b61, 0c24b82bc4d12c6a58ceacbf2598cd4df63abf9a, 0c25ab93f2878cab07d37ca5afd302283201e5af 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: atomisp: Add check for rgby_data memory allocation failure In ia_css_3a_statistics_allocate(), there is no check on the allocation result of the rgby_data memory. If rgby_data is not successfully allocated, it may trigger the assert(host_stats->rgby_data) assertion in ia_css_s3a_hmem_decode(). Adding a check to fix this potential issue.
- Published
- Dec 28, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-617
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.8 and later · before 5.10.231
- linux linux kernel5.11 and later · before 5.15.174
- linux linux kernel5.16 and later · before 6.1.120
- linux linux kernel4.12 and later · before 4.18
- linux linux kernel6.7 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
- linux linux kernel6.2 and later · before 6.6.64
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
- 4.12, 5.8affected
- a49d25364dfb9f8a64037488a39ab1f56c5fa419 and later · before 51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654affected · git
- ad85094b293e40e7a2f831b0311a389d952ebd5e and later · before 0c24b82bc4d12c6a58ceacbf2598cd4df63abf9aaffected · git
- ad85094b293e40e7a2f831b0311a389d952ebd5e and later · before 4676e50444046b498555b849e6080a5c78cdda9baffected · git
- ad85094b293e40e7a2f831b0311a389d952ebd5e and later · before 02a97d9d7ff605fa4a1f908d1bd3ad8573234b61affected · git
- ad85094b293e40e7a2f831b0311a389d952ebd5e and later · before 8066badaf7463194473fb4be19dbe50b11969aa0affected · git
- ad85094b293e40e7a2f831b0311a389d952ebd5e and later · before 74aa783682c4d78c69d87898e40c78df1fec204eaffected · git
- ad85094b293e40e7a2f831b0311a389d952ebd5e and later · before 0c25ab93f2878cab07d37ca5afd302283201e5afaffected · git
- ad85094b293e40e7a2f831b0311a389d952ebd5e and later · before ed61c59139509f76d3592683c90dc3fdc6e23cd6affected · git
- before 4.12not 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 6.1.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2024-56701Dec 28, 2024 · powerpc/pseries: Fix dtl_access_lock to be a rw_semaphore22Monitor
- ← EarlierCVE-2024-56704Dec 28, 2024 · 9p/xen: fix release of IRQ31Monitor
- Later →CVE-2024-56706Dec 28, 2024 · s390/cpum_sf: Fix and protect memory allocation of SDBs with mutex25Monitor
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 | 02a97d9d7ff605fa4a1f908d1bd3ad8573234b61 | Vendor (CNA) |
| Linux Linux | 0c24b82bc4d12c6a58ceacbf2598cd4df63abf9a | Vendor (CNA) |
| Linux Linux | 0c25ab93f2878cab07d37ca5afd302283201e5af | Vendor (CNA) |
| Linux Linux | 4676e50444046b498555b849e6080a5c78cdda9b | Vendor (CNA) |
| Linux Linux | 51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654 | Vendor (CNA) |
| Linux Linux | 74aa783682c4d78c69d87898e40c78df1fec204e | Vendor (CNA) |
| Linux Linux | 8066badaf7463194473fb4be19dbe50b11969aa0 | Vendor (CNA) |
| Linux Linux | ed61c59139509f76d3592683c90dc3fdc6e23cd6 | Vendor (CNA) |
| debian:linux | 6.1.123-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.
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 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.
- CVE-2026-31739489 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC35Monitor
- CVE-2025-39803261 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2023-52621277 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers31Monitor
- CVE-2026-31398461 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios31Monitor
- CVE-2026-46117516 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()31Monitor
- CVE-2026-46027515 days apartnet/smc: avoid early lgr access in smc_clc_wait_msg30Monitor
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)
CWE-617 · Reachable AssertionCVSS 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 (9 more)Show less
- git.kernel.org/stable/c/0c24b82bc4d12c6a58ceacbf2598cd4df63abf9a
- git.kernel.org/stable/c/0c25ab93f2878cab07d37ca5afd302283201e5af
- git.kernel.org/stable/c/4676e50444046b498555b849e6080a5c78cdda9b
- git.kernel.org/stable/c/51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654
- git.kernel.org/stable/c/74aa783682c4d78c69d87898e40c78df1fec204e
- git.kernel.org/stable/c/8066badaf7463194473fb4be19dbe50b11969aa0
- git.kernel.org/stable/c/ed61c59139509f76d3592683c90dc3fdc6e23cd6
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.