CVE-2023-53637: media: i2c: ov772x: Fix memleak in ov772x_probe()
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.20% (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 1da495101ef7507eb4f4b1dbec2874d740eff251, 448ce1cd50387b1345ec14eb191ef05f7afc2a26, 7485edb2b6ca5960205c0a49bedfd09bba30e521.
Low priority for now. Upgrade to Linux Linux 1da495101ef7507eb4f4b1dbec2874d740eff251, 448ce1cd50387b1345ec14eb191ef05f7afc2a26, 7485edb2b6ca5960205c0a49bedfd09bba30e521 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: i2c: ov772x: Fix memleak in ov772x_probe() A memory leak was reported when testing ov772x with bpf mock device: AssertionError: unreferenced object 0xffff888109afa7a8 (size 8): comm "python3", pid 279, jiffies 4294805921 (age 20.681s) hex dump (first 8 bytes): 80 22 88 15 81 88 ff ff ."...... backtrace: [<000000009990b438>] __kmalloc_node+0x44/0x1b0 [<000000009e32f7d7>] kvmalloc_node+0x34/0x180 [<00000000faf48134>] v4l2_ctrl_handler_init_class+0x11d/0x180 [videodev] [<00000000da376937>] ov772x_probe+0x1c3/0x68c [ov772x] [<000000003f0d225e>] i2c_device_probe+0x28d/0x680 [<00000000e0b6db89>] really_probe+0x17c/0x3f0 [<000000001b19fcee>] __driver_probe_device+0xe3/0x170 [<0000000048370519>] driver_probe_device+0x49/0x120 [<000000005ead07a0>] __device_attach_driver+0xf7/0x150 [<0000000043f452b8>] bus_for_each_drv+0x114/0x180 [<00000000358e5596>] __device_attach+0x1e5/0x2d0 [<0000000043f83c5d>] bus_probe_device+0x126/0x140 [<00000000ee0f3046>] device_add+0x810/0x1130 [<00000000e0278184>] i2c_new_client_device+0x359/0x4f0 [<0000000070baf34f>] of_i2c_register_device+0xf1/0x110 [<00000000a9f2159d>] of_i2c_notify+0x100/0x160 unreferenced object 0xffff888119825c00 (size 256): comm "python3", pid 279, jiffies 4294805921 (age 20.681s) hex dump (first 32 bytes): 00 b4 a5 17 81 88 ff ff 00 5e 82 19 81 88 ff ff .........^...... 10 5c 82 19 81 88 ff ff 10 5c 82 19 81 88 ff ff .\.......\...... backtrace: [<000000009990b438>] __kmalloc_node+0x44/0x1b0 [<000000009e32f7d7>] kvmalloc_node+0x34/0x180 [<0000000073d88e0b>] v4l2_ctrl_new.cold+0x19b/0x86f [videodev] [<00000000b1f576fb>] v4l2_ctrl_new_std+0x16f/0x210 [videodev] [<00000000caf7ac99>] ov772x_probe+0x1fa/0x68c [ov772x] [<000000003f0d225e>] i2c_device_probe+0x28d/0x680 [<00000000e0b6db89>] really_probe+0x17c/0x3f0 [<000000001b19fcee>] __driver_probe_device+0xe3/0x170 [<0000000048370519>] driver_probe_device+0x49/0x120 [<000000005ead07a0>] __device_attach_driver+0xf7/0x150 [<0000000043f452b8>] bus_for_each_drv+0x114/0x180 [<00000000358e5596>] __device_attach+0x1e5/0x2d0 [<0000000043f83c5d>] bus_probe_device+0x126/0x140 [<00000000ee0f3046>] device_add+0x810/0x1130 [<00000000e0278184>] i2c_new_client_device+0x359/0x4f0 [<0000000070baf34f>] of_i2c_register_device+0xf1/0x110 The reason is that if priv->hdl.error is set, ov772x_probe() jumps to the error_mutex_destroy without doing v4l2_ctrl_handler_free(), and all resources allocated in v4l2_ctrl_handler_init() and v4l2_ctrl_new_std() are leaked.
- Published
- Oct 7, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-401
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 kernel4.17 and later · before 4.19.276
- linux linux kernel4.20 and later · before 5.4.235
- linux linux kernel5.5 and later · before 5.10.173
- linux linux kernel5.11 and later · before 5.15.99
- linux linux kernel5.16 and later · before 6.1.16
- linux linux kernel6.2 and later · before 6.2.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
- 4.17affected
- 1112babde21483d86ed3fbad1320b0ddf9ab2ece and later · before cc3b6011d7a9f149489eb9420c6305a779162c57affected · git
- 1112babde21483d86ed3fbad1320b0ddf9ab2ece and later · before 448ce1cd50387b1345ec14eb191ef05f7afc2a26affected · git
- 1112babde21483d86ed3fbad1320b0ddf9ab2ece and later · before dfaafeb8e9537969e8dba75491f732478c7fa9d6affected · git
- 1112babde21483d86ed3fbad1320b0ddf9ab2ece and later · before 1da495101ef7507eb4f4b1dbec2874d740eff251affected · git
- 1112babde21483d86ed3fbad1320b0ddf9ab2ece and later · before ac93f8ac66e60227bed42d5a023f0e6c15b52c0aaffected · git
- 1112babde21483d86ed3fbad1320b0ddf9ab2ece and later · before c86d760c1c6855a6131e78d0ddacc48c79324ac3affected · git
- 1112babde21483d86ed3fbad1320b0ddf9ab2ece and later · before 7485edb2b6ca5960205c0a49bedfd09bba30e521affected · git
- before 4.17not affected · semver
- 4.19.276 and later · up to and including 4.19.*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 6.1.20-1 | 6.1.20-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-2023-53634Oct 7, 2025 · bpf, arm64: Fixed a BTI error on returning to patched function22Monitor
- ← EarlierCVE-2023-53636Oct 7, 2025 · clk: microchip: fix potential UAF in auxdev release callback31Monitor
- Later →CVE-2023-53639Oct 7, 2025 · wifi: ath6kl: reduce WARN to dev_dbg() in callback22Monitor
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 | 1da495101ef7507eb4f4b1dbec2874d740eff251 | Vendor (CNA) |
| Linux Linux | 448ce1cd50387b1345ec14eb191ef05f7afc2a26 | Vendor (CNA) |
| Linux Linux | 7485edb2b6ca5960205c0a49bedfd09bba30e521 | Vendor (CNA) |
| Linux Linux | ac93f8ac66e60227bed42d5a023f0e6c15b52c0a | Vendor (CNA) |
| Linux Linux | c86d760c1c6855a6131e78d0ddacc48c79324ac3 | Vendor (CNA) |
| Linux Linux | cc3b6011d7a9f149489eb9420c6305a779162c57 | Vendor (CNA) |
| Linux Linux | dfaafeb8e9537969e8dba75491f732478c7fa9d6 | Vendor (CNA) |
| debian:linux | 6.1.20-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)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS 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 (6 more)Show less
- git.kernel.org/stable/c/448ce1cd50387b1345ec14eb191ef05f7afc2a26
- git.kernel.org/stable/c/7485edb2b6ca5960205c0a49bedfd09bba30e521
- git.kernel.org/stable/c/ac93f8ac66e60227bed42d5a023f0e6c15b52c0a
- git.kernel.org/stable/c/c86d760c1c6855a6131e78d0ddacc48c79324ac3
- git.kernel.org/stable/c/cc3b6011d7a9f149489eb9420c6305a779162c57
- git.kernel.org/stable/c/dfaafeb8e9537969e8dba75491f732478c7fa9d6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.