CVE-2024-46677: gtp: fix a potential NULL pointer dereference
Published Sep 13, 2024
·Updated
gtp: fix a potential NULL pointer dereference
Affected Software
19 affected componentsFixes available
Linux Linux kernel>=4.12<4.19.321
Linux Linux kernel>=4.20<5.4.283
Linux Linux kernel>=5.5<5.10.225
Linux Linux kernel>=5.11<5.15.166
Linux Linux kernel>=5.16<6.1.108
Linux Linux kernel>=6.2<6.6.49
Linux Linux kernel>=6.7<6.10.8
Linux Linux kernel=6.11-rc1
Linux Linux kernel=6.11-rc2
Linux Linux kernel=6.11-rc3
Linux Linux kernel=6.11-rc4
Linux Linux kernel=6.11-rc5
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft azl3 kernel 6.6.47.1-1
Microsoft cbl2 kernel 5.15.164.1-1
Microsoft cbl2 kernel 5.15.164.1-1
Microsoft cbl2 kernel 5.15.167.1-1
Microsoft azl3 kernel 6.6.51.1-1
Remediation
Event History
Sep 13, 2024
CVE Published
via MITRE·05:29 AM
Data Sourced
via MITRE·05:29 AM
Description
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 12, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Apr 27, 2025
Data Sourced
via Ubuntu·12:35 AM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-46677?
CVE-2024-46677 has been classified with a high severity level due to the potential for NULL pointer dereference in the Linux kernel.
2
How do I fix CVE-2024-46677?
To fix CVE-2024-46677, update your Linux kernel to versions 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1 as outlined in the vulnerability report.
3
What software versions are affected by CVE-2024-46677?
CVE-2024-46677 affects various versions of the Linux kernel from 4.12 up to 6.1.
4
Are all Linux distributions affected by CVE-2024-46677?
Not all Linux distributions are affected; specific versions of Debian and other distributions running vulnerable kernel versions are impacted.
5
Is there a workaround for CVE-2024-46677 if I can't update?
While the best course of action is to update, there are no specific workarounds documented for CVE-2024-46677.