CVE-2026-74398

CVE CVE-2026-74398EUVD EUVD-2026-59545Published 2026-08-15T05:59:10.000ZLast changed 2026-08-17T05:46:43.000ZCVSS 9.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD addrconf_dad_failure() transitions ifp->state from DAD to POSTDAD via addrconf_dad_end(), which drops ifp->lock on return. The lock is re-acquired after net_info_ratelimited(). A concurrent ipv6_del_addr() can take the lock in that window, set ifp->state to DEAD and run list_del_rcu(&ifp->if_list). addrconf_dad_failure() then overwrites DEAD with ERRDAD at errdad: and schedules a new dad_work. The work calls ipv6_del_addr() again, hitting the already-poisoned list entry: general protection fault: 0000 [#1] SMP NOPTI CPU: 4 PID: 217 Comm: kworker/4:1 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:ipv6_del_addr+0xe9/0x280 RAX: dead000000000122 Call Trace: addrconf_dad_stop+0x113/0x140 addrconf_dad_work+0x28c/0x430 process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ret_from_fork+0x35/0x40 Fold the addrconf_dad_end() logic into addrconf_dad_failure() under a single ifp->lock critical section. The STABLE_PRIVACY branch temporarily drops ifp->lock around address regeneration, so at lock_errdad: verify the state is still POSTDAD before transitioning to ERRDAD; bail out otherwise to avoid overwriting a state set by another path while the lock was released.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 835b474b8f70fa68d68abffad37378e92f661802; c15b1ccadb323ea50023e8f1cca2954129a62b51 <8ed0ce9ea58d677d1bac92614ee5f60f8ea57363; c15b1ccadb323ea50023e8f1cca2954129a62b51 <e889aa99ad3ed48bb0ddcff6475b17542532d18b; 3.10.105 <3.11; patch: 6.1.178; patch: 7.2; patch: 0; c15b1ccadb323ea50023e8f1cca2954129a62b51 <3bdc86d89fd6c6523753fa6f42fcfaf30ee699cb; patch: 5.10.261; c15b1ccadb323ea50023e8f1cca2954129a62b51 <47b05836705b63dab93d9ac7c69a3a507375ef80; c15b1ccadb323ea50023e8f1cca2954129a62b51 <d21be7d051012c6b572fa4e3334443c250216f7b; patch: 6.6.145; c15b1ccadb323ea50023e8f1cca2954129a62b51 <627ac78f2741e2ebd2225e2e953b6964a8a9182f; patch: 5.15.212; c15b1ccadb323ea50023e8f1cca2954129a62b51 <875c284c0f98b042bb97abad460f63a24c977f88; patch: 6.12.97; 3.14; patch: 6.18.40; c15b1ccadb323ea50023e8f1cca2954129a62b51 <b61af0268e3d1308c466bf0be5dced844eafc1ef; patch: 7.1.5

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.