| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Use after free in Windows Resilient File System (ReFS) allows an authorized attacker to elevate privileges locally. |
| Use after free in Windows Secure Socket Tunneling Protocol (SSTP) allows an authorized attacker to elevate privileges locally. |
| Use after free in Windows iSCSI allows an unauthorized attacker to execute code over a network. |
| Integer overflow or wraparound in Windows Network Connection Broker allows an authorized attacker to elevate privileges locally. |
| Use after free in Windows System Events Broker allows an authorized attacker to disclose information locally. |
| Use after free in Microsoft Office allows an unauthorized attacker to execute code over a network. |
| Use after free in Microsoft Office allows an unauthorized attacker to execute code over a network. |
| In the Linux kernel, the following vulnerability has been resolved:
bpf: Reject resilient lock operations in rbtree callbacks
__bpf_rbtree_add() keeps parent and link pointers live across calls to the
program-supplied comparison callback. The verifier therefore requires the
root's lock to remain held throughout the callback.
The helper path enforces this rule for bpf_spin_lock() and
bpf_spin_unlock(), but the resilient lock kfunc argument path does not.
Since resilient locks may protect BPF rbtree roots, a callback can release
the root lock and let another CPU remove and free the node referenced by
the in-progress tree walk. The walk then resumes using freed pointers.
Reject resilient lock kfuncs in an rbtree comparison callback, matching
the existing policy for the spin lock helpers. Resilient-lock-protected
trees remain valid when their comparison callbacks leave lock state alone. |
| In the Linux kernel, the following vulnerability has been resolved:
tracing/probes: Fix use-after-free on field name/type of events with multiple probes
The fields of a probe-based dynamic event (kprobe, uprobe, eprobe and
fprobe events) are created in traceprobe_define_arg_fields() by handing
the probe_arg name/type strings to trace_define_field(), which only
stores the pointers without copying. Those strings are owned by the
trace_probe and are freed when that probe is removed.
An event can have several probes attached. The field list is defined
only once, by the first probe that registers the event, but it is kept
alive by any surviving sibling probe. Deleting just that first probe by
symbol -
# primary A: fields are defined from A's args
echo 'p:kprobes/ev vfs_read a1=$arg1' > kprobe_events
# append B: shares A's event call
echo 'p:kprobes/ev vfs_write a1=$arg1' >> kprobe_events
# delete only A (matched by symbol), B survives
echo '-:kprobes/ev vfs_read' >> kprobe_events
frees A's args (trace_probe_cleanup() -> traceprobe_free_probe_arg()),
but trace_probe_unlink() keeps the trace_probe_event because the probe
list is not empty. The event call stays registered via B while its
fields now reference freed memory. Any field lookup then reads it, e.g.
echo 'a1 == 1' > events/kprobes/ev/filter
BUG: KASAN: slab-use-after-free in strcmp+0xa7/0xb0
Call Trace:
strcmp
trace_find_event_field
parse_pred
process_preds
create_filter
apply_event_filter
event_filter_write
field->name references parg->name (kstrdup'd, freed with the probe) and,
for array arguments, field->type references parg->fmt (kmalloc'd, freed
with the probe) - the scalar type otherwise points at the static
fmttype rodata, which is safe.
Have traceprobe_define_arg_fields() duplicate the name and type strings
and anchor the copies on the trace_probe_event, which embeds the event
call and outlives every individual probe; trace_probe_event_free()
releases them.
The reproducer above triggers reliably; the field lookup and the delete
both run under event_mutex, so this is a dangling reference after
removal rather than a race.
The issue was found by the autokbug dynamic kernel fuzzer at Tencent
Yunding Lab. |
| A use-after-free was found in libeot, a library that converts Embedded OpenType (EOT) fonts. Processing a specially crafted font file can cause the library to access memory after it has been freed, resulting in a crash or possible memory corruption. |
| Poppler through 26.11.0 contains a use-after-free vulnerability in NSSCryptoSignBackend.cc that allows attackers to trigger reads of freed CMS arena memory during repeated signature verification. Attackers can supply a signed PDF embedding the signer certificate to crash applications or pdfsig runs validating multiple signatures, or cause incorrect certificate validation results. |
| Use after free in Windows MIDI Service Module allows an authorized attacker to elevate privileges locally. |
| Use after free in Windows Print Spooler Components allows an authorized attacker to elevate privileges locally. |
| Use after free in Windows MIDI Service Module allows an authorized attacker to elevate privileges locally. |
| Use after free in Windows Wireless Networking allows an authorized attacker to elevate privileges locally. |
| Use after free in Windows Kernel allows an authorized attacker to elevate privileges locally. |
| Use after free in Windows Network Connection Broker allows an authorized attacker to elevate privileges locally. |
| Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.
Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.
CWE: CWE-416: Use After Free
Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.
If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough. This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.
An application that then reads or frees the stack will use memory that
was already freed. This can crash the application or, in principle,
corrupt memory.
Only applications that pass a stack that is not NULL are affected.
OpenSSL itself never does this. Its own callers, including the code that
TLS uses to load CA certificates, always pass NULL. When the stack is
NULL, the function frees only the entries that it created itself, which
is safe. We expect that very few applications pass an existing stack. An
attacker can make the read fail with malformed PEM data, but cannot make
an application pass an existing stack.
The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()
and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and
1.0.2 have only the first two of these functions.
FIPS impact: no
The affected code is outside the FIPS module boundary. |
| In FRRouting, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a "bgp listen range" also has a Site-of-Origin configured ("neighbor PG soo"). Each dynamic neighbor shares the peer-group's SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. The first disconnect leaves the peer-group pointing at freed memory, and the second disconnect frees it again, causing bgpd to abort and drop all BGP sessions on the router. Any host whose address falls inside the listen range can trigger this by opening and closing two TCP connections to the BGP port, without sending any BGP message and without knowing the AS number, and can repeat it each time bgpd restarts. If the peer-group has a TCP-MD5 password, only hosts that know the password can trigger it. Two ordinary flaps of legitimate dynamic neighbors have the same effect. Between the two frees, displaying the configuration ("show running-config") or establishing a dynamic neighbor also reads the freed memory, which can crash bgpd after a single disconnect. Only configurations that combine a listen range with a SoO on the same peer-group are affected. |
| GPAC before 26.07.0 contains a use-after-free vulnerability in xmt_parse_command() in loader_xmt.c that allows attackers to access freed memory via a dangling command buffer pointer. Attackers can supply a crafted XMT scene file whose Replace command frees a Conditional node, crashing MP4Box and potentially corrupting the heap. |