344 matches found
CVE-2025-21761 openvswitch: use RCU protection in ovs_vport_cmd_fill_info()
In the Linux kernel, the following vulnerability has been resolved: openvswitch: use RCU protection in ovsvportcmdfillinfo ovsvportcmdfillinfo can be called without RTNL or RCU. Use RCU protection and devnetrcu to avoid potential UAF...
CVE-2025-21762
In the Linux kernel, the following vulnerability has been resolved: arp: use RCU protection in arpxmit arpxmit can be called without RTNL or RCU protection. Use RCU protection to avoid potential UAF...
CVE-2025-21761
In the Linux kernel, the following vulnerability has been resolved: openvswitch: use RCU protection in ovsvportcmdfillinfo ovsvportcmdfillinfo can be called without RTNL or RCU. Use RCU protection and devnetrcu to avoid potential UAF...
CVE-2025-21760 ndisc: extend RCU protection in ndisc_send_skb()
In the Linux kernel, the following vulnerability has been resolved: ndisc: extend RCU protection in ndiscsendskb ndiscsendskb can be called without RTNL or RCU held. Acquire rcureadlock earlier, so that we can use devnetrcu and avoid a potential UAF...
CVE-2025-21760
CVE-2025-21760: Linux kernel vulnerability in NDISC code. The issue arises because ndisc_send_skb() could be called without RTNL or RCU held, risking use-after-free. The fix adds acquiring rcu_read_lock() earlier to enable use of dev_net_rcu() and prevent UAF. Connected docs also reference relate...
CVE-2025-21760 ndisc: extend RCU protection in ndisc_send_skb()
In the Linux kernel, the following vulnerability has been resolved: ndisc: extend RCU protection in ndiscsendskb ndiscsendskb can be called without RTNL or RCU held. Acquire rcureadlock earlier, so that we can use devnetrcu and avoid a potential UAF...
CVE-2025-21760 ndisc: extend RCU protection in ndisc_send_skb()
In the Linux kernel, the following vulnerability has been resolved: ndisc: extend RCU protection in ndiscsendskb ndiscsendskb can be called without RTNL or RCU held. Acquire rcureadlock earlier, so that we can use devnetrcu and avoid a potential UAF...
CVE-2025-21760
In the Linux kernel, the following vulnerability has been resolved: ndisc: extend RCU protection in ndiscsendskb ndiscsendskb can be called without RTNL or RCU held. Acquire rcureadlock earlier, so that we can use devnetrcu and avoid a potential UAF...
CVE-2025-21759
CVE-2025-21759: In the Linux kernel, ipv6 mcast path igmp6_send() could be invoked without RTNL/RCU held, risking use-after-free of the net pointer. The fix extends RCU protection to safely fetch the net pointer and avoid UAF, and replaces sock_alloc_send_skb usage with alloc_skb under RCU protec...
CVE-2025-21758
CVE-2025-21758 : Linux kernel vulnerability where ipv6 multicast handling (mld_newpack) could be called without RTNL or RCU protection. The fix adds RCU protection to mld_newpack and changes allocations from GFP_KERNEL to alloc_skb, charging the net->ipv6.igmp_sk socket under RCU protection. P...
CVE-2025-21758 ipv6: mcast: add RCU protection to mld_newpack()
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: add RCU protection to mldnewpack mldnewpack can be called without RTNL or RCU being held. Note that we no longer can use sockallocsendskb because ipv6.igmpsk uses GFPKERNEL allocations which can sleep. Instead use...
CVE-2025-21759 ipv6: mcast: extend RCU protection in igmp6_send()
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: extend RCU protection in igmp6send igmp6send can be called without RTNL or RCU being held. Extend RCU protection so that we can safely fetch the net pointer and avoid a potential UAF. Note that we no longer can use...
CVE-2025-21759 ipv6: mcast: extend RCU protection in igmp6_send()
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: extend RCU protection in igmp6send igmp6send can be called without RTNL or RCU being held. Extend RCU protection so that we can safely fetch the net pointer and avoid a potential UAF. Note that we no longer can use...
CVE-2025-21759 ipv6: mcast: extend RCU protection in igmp6_send()
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: extend RCU protection in igmp6send igmp6send can be called without RTNL or RCU being held. Extend RCU protection so that we can safely fetch the net pointer and avoid a potential UAF. Note that we no longer can use...
CVE-2025-21758 ipv6: mcast: add RCU protection to mld_newpack()
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: add RCU protection to mldnewpack mldnewpack can be called without RTNL or RCU being held. Note that we no longer can use sockallocsendskb because ipv6.igmpsk uses GFPKERNEL allocations which can sleep. Instead use...
CVE-2025-21758
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: add RCU protection to mldnewpack mldnewpack can be called without RTNL or RCU being held. Note that we no longer can use sockallocsendskb because ipv6.igmpsk uses GFPKERNEL allocations which can sleep. Instead use...
CVE-2025-21759
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: extend RCU protection in igmp6send igmp6send can be called without RTNL or RCU being held. Extend RCU protection so that we can safely fetch the net pointer and avoid a potential UAF. Note that we no longer can use...
CVE-2022-49456
In the Linux kernel, the following vulnerability has been resolved: bonding: fix missed rcu protection When removing the rcureadlock in bondethtoolgettsinfo as discussed 1, I didn't notice it could be called via setsockopt, which doesn't hold rcu lock, as syzbot pointed: stack backtrace: CPU: 0...
DEBIAN-CVE-2022-49456
In the Linux kernel, the following vulnerability has been resolved: bonding: fix missed rcu protection When removing the rcureadlock in bondethtoolgettsinfo as discussed 1, I didn't notice it could be called via setsockopt, which doesn't hold rcu lock, as syzbot pointed: stack backtrace: CPU: 0...
CVE-2022-49456 bonding: fix missed rcu protection
In the Linux kernel, the following vulnerability has been resolved: bonding: fix missed rcu protection When removing the rcureadlock in bondethtoolgettsinfo as discussed 1, I didn't notice it could be called via setsockopt, which doesn't hold rcu lock, as syzbot pointed: stack backtrace: CPU: 0...