The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsThere is no fixed version for Centos:7
kernel-rt-trace-devel
.
Note: Versions mentioned in the description apply only to the upstream kernel-rt-trace-devel
package and not the kernel-rt-trace-devel
package as distributed by Centos
.
See How to fix?
for Centos:7
relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
ipv6: fix memory leak in fib6_rule_suppress
The kernel leaks memory when a fib
rule is present in IPv6 nftables
firewall rules and a suppress_prefix rule is present in the IPv6 routing
rules (used by certain tools such as wg-quick). In such scenarios, every
incoming packet will leak an allocation in ip6_dst_cache
slab cache.
After some hours of bpftrace
-ing and source code reading, I tracked
down the issue to ca7a03c41753 ("ipv6: do not free rt if
FIB_LOOKUP_NOREF is set on suppress rule").
The problem with that change is that the generic args->flags
always have
FIB_LOOKUP_NOREF
set1 but the IPv6-specific flag
RT6_LOOKUP_F_DST_NOREF
might not be, leading to fib6_rule_suppress
not
decreasing the refcount when needed.
How to reproduce:
sudo slabtop -o | grep ip6_dst_cache
to see memory usage increase
with every incoming ipv6 packet.This patch exposes the protocol-specific flags to the protocol
specific suppress
function, and check the protocol-specific flags
argument for RT6_LOOKUP_F_DST_NOREF instead of the generic
FIB_LOOKUP_NOREF when decreasing the refcount, like this.