CVE-2022-50163: ax25: fix incorrect dev_tracker usage
Published Jun 18, 2025
·Updated
ax25: fix incorrect devtracker usage
Affected Software
14 affected components
Linux Linux kernel
Linux Linux kernel>=4.14.277<4.15
Linux Linux kernel>=4.19.240<4.20
Linux Linux kernel>=5.4.190<5.5
Linux Linux kernel>=5.10.112<5.11
Linux Linux kernel>=5.15.35<5.16
Linux Linux kernel>=5.17.1<5.18.18
Linux Linux kernel>=5.19<5.19.2
Linux Linux kernel=5.17
Linux Linux kernel=5.17-rc4
Linux Linux kernel=5.17-rc5
Linux Linux kernel=5.17-rc6
Linux Linux kernel=5.17-rc7
Linux Linux kernel=5.17-rc8
Remediation
Event History
Jun 18, 2025
CVE Published
via MITRE·11:03 AM
Data Sourced
via MITRE·11:03 AM
Description
Data Sourced
via NVD·11:15 AM
RemedyDescriptionSeverityAffected Software
Nov 20, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2022-50163?
CVE-2022-50163 has a moderate severity rating due to the potential for incorrect device tracking affecting system stability.
2
How do I fix CVE-2022-50163?
To fix CVE-2022-50163, update to the latest version of the Linux kernel that includes the patch addressing this vulnerability.
3
What software is affected by CVE-2022-50163?
CVE-2022-50163 affects the Linux kernel when the ax25 protocol is in use.
4
Can CVE-2022-50163 lead to a denial of service?
Yes, CVE-2022-50163 can potentially lead to a denial of service due to improper device reference counting.
5
Is CVE-2022-50163 exploitable remotely?
CVE-2022-50163 is not classified as remotely exploitable since it requires local access to the affected device.