Bug 1221651 (CVE-2024-26634) - VUL-0: CVE-2024-26634: kernel: net: fix removing a namespace with conflicting altnames
Summary: VUL-0: CVE-2024-26634: kernel: net: fix removing a namespace with conflicting...
Status: RESOLVED FIXED
Alias: CVE-2024-26634
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/398040/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-26634:5.5:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-19 07:17 UTC by SMASH SMASH
Modified: 2024-06-10 10:28 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-03-19 07:17:41 UTC
In the Linux kernel, the following vulnerability has been resolved:

net: fix removing a namespace with conflicting altnames

Mark reports a BUG() when a net namespace is removed.

    kernel BUG at net/core/dev.c:11520!

Physical interfaces moved outside of init_net get "refunded"
to init_net when that namespace disappears. The main interface
name may get overwritten in the process if it would have
conflicted. We need to also discard all conflicting altnames.
Recent fixes addressed ensuring that altnames get moved
with the main interface, which surfaced this problem.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-26634
https://www.cve.org/CVERecord?id=CVE-2024-26634
https://git.kernel.org/stable/c/8072699aa9e67d1727692cfb3c347263bb627fb9
https://git.kernel.org/stable/c/a2232f29bf52c24f827865b3c90829c44b6c695b
https://git.kernel.org/stable/c/d09486a04f5da0a812c26217213b89a3b1acf836
https://git.kernel.org/stable/c/e855dded4b70d1975ee7b9fed0c700391e3c8ea6
https://bugzilla.redhat.com/show_bug.cgi?id=2270116
Comment 1 Carlos López 2024-03-19 07:18:20 UTC
The bug was never introduced in SLE15-SP6 or older, so we are not affected. Already fixed in stable.
Comment 3 Andrea Mattiazzo 2024-06-10 10:28:34 UTC
All done, closing.