CVE-2022-49046
i2c: dev: check return value when calling dev_set_name()
MEDIUM
5.5
CVSS Score
Published: February 26, 2025 at 01:54 AM UTC
Updated: June 17, 2026 at 05:16 AM UTC
1 product affected across 1 vendorLinux Kernel
Using Linux by Linux?
Get instant alerts when new vulnerabilities affect Linux - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.3%
Description
In the Linux kernel, the following vulnerability has been resolved: i2c: dev: check return value when calling dev_set_name() If dev_set_name() fails, the dev_name() is null, check the return value of dev_set_name() to avoid the null-ptr-deref.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
v ≥ 4.14.182v ≥ 4.19.125v ≥ 4.4.225v ≥ 4.9.225v ≥ 5.4.43v ≥ 5.6.154.14.182 ≤ v < 4.154.19.125 ≤ v < 4.204.4.225 ≤ v < 4.54.9.225 ≤ v < 4.105.16 ≤ v < 5.17.45.4.43 ≤ v < 5.55.6.15 ≤ v < 5.15.355.6.15 ≤ v < 5.75.7 ≤ v < 5.10.2365.7 ≤ v < 5.15.355.7 ≤ v < 5.17.45.7 ≤ v < 5.181413ef638abae4ab5621901cf4d8ef08a4a48ba61bed86cfe5cb4529d036a14980d379aee85399821c1b4327970c79c1a2d0c3becfc12b9696177c554.14.1824.19.1254.4.2254.9.2255.18 rc15.18 rc25.4.435.6.158a231148135d2d08a3ef721d438cd468ea4209d2a612c4ece2eb757011ae88a8410b48e523220b8dc0d34399045609eda76882fa6d01fdfaf5b20d38f1f3b4150baf7c3aa6b4e6b81b8ff1909996d507
Vendor states this is fixed in 2e539b17d4cbe5fb8b5152dd9a6e4a8828f97db2 (fixed)
Vendor states this is fixed in 2f345bb14ad4744950499ff222e2899209297afa (fixed)
Vendor states this is fixed in 993eb48fa199b5f476df8204e652eff63dd19361 (fixed)
Vendor states this is fixed in c74d77a2d07744147d734138acd6ce9dba715e5d (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.236 (unaffected)
Vendor states this is fixed in 5.15.35 (unaffected)
Vendor states this is fixed in 5.17.4 (unaffected)
Vendor states this is fixed in 5.18 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.7 (unaffected)
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (5)
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2e539b17d4cbe5fb8b5152dd9a6e4a8828f97db2Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2f345bb14ad4744950499ff222e2899209297afaPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/993eb48fa199b5f476df8204e652eff63dd19361Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c74d77a2d07744147d734138acd6ce9dba715e5dSource: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/05/msg00030.htmlCVSS
- Attack Vector
- LOCAL
- Complexity
- LOW
- Privileges
- LOW
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- NONE
- Integrity
- NONE
- Availability
- HIGH
Vector?
Quick Info
StatusMODIFIED
CWE
CWE-476
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card