A vulnerability in the h5dump tool of HDF5 before version 2.1.1 allows denial of service via untrusted pointer dereference. This occurs when dumping a variable-length string dataset with multiple elements in binary mode, causing corrupted stride calculation and misaligned pointer dereference.
Mozilla Thunderbird contained a critical heap buffer overflow vulnerability (CVE-2026-103500) triggered by opening an email of size 2GB or larger. This flaw allows remote attackers to cause severe impact including full confidentiality, integrity, and availability compromise. The issue was fixed in Thunderbird versions 157, 140.17, and 153.4.
Multiple critical security vulnerabilities affecting Mozilla Firefox were fixed in Firefox ESR 153.4 and Firefox 157. These include sandbox escapes, use-after-free bugs, mitigation bypasses, same-origin policy bypass, denial-of-service, privilege escalation, and cryptography misuse across various components such as the JavaScript engine, DOM, graphics, storage, and networking. The vulnerabilities could allow remote attackers to execute arbitrary code, escalate privileges, bypass security mitigations, or cause denial of service. The issues affect versions prior to Firefox ESR 153.4 and Firefox 157.
Multiple security vulnerabilities in the Linux kernel have been resolved, including a flaw in the ASoC topology parser that could lead to out-of-bounds reads due to non-NUL-terminated PCM and DAI name fields. Additional fixes address an inode lock leak in the XFS quota subsystem and double free issues in the DMA engine idxd driver. These vulnerabilities have been patched in specific kernel versions.
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode
Currently, whenever there is a need to transmit an Action frame,
the brcmfmac driver always uses the P2P vif to send the "actframe" IOVAR to
firmware. The P2P interfaces were available when wpa_supplicant is managing
the wlan interface.
However, the P2P interfaces are not created/initialized when only hostapd
is managing the wlan interface. And if hostapd receives an ANQP Query REQ
Action frame even from an un-associated STA, the brcmfmac driver tries
to use an uninitialized P2P vif pointer for sending the IOVAR to firmware.
This NULL pointer dereferencing triggers a driver crash.
[ 1417.074538] Unable to handle kernel NULL pointer dereference at virtual
address 0000000000000000
[...]
[ 1417.075188] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT)
[...]
[ 1417.075653] Call trace:
[ 1417.075662] brcmf_p2p_send_action_frame+0x23c/0xc58 [brcmfmac]
[ 1417.075738] brcmf_cfg80211_mgmt_tx+0x304/0x5c0 [brcmfmac]
[ 1417.075810] cfg80211_mlme_mgmt_tx+0x1b0/0x428 [cfg80211]
[ 1417.076067] nl80211_tx_mgmt+0x238/0x388 [cfg80211]
[ 1417.076281] genl_family_rcv_msg_doit+0xe0/0x158
[ 1417.076302] genl_rcv_msg+0x220/0x2a0
[ 1417.076317] netlink_rcv_skb+0x68/0x140
[ 1417.076330] genl_rcv+0x40/0x60
[ 1417.076343] netlink_unicast+0x330/0x3b8
[ 1417.076357] netlink_sendmsg+0x19c/0x3f8
[ 1417.076370] __sock_sendmsg+0x64/0xc0
[ 1417.076391] ____sys_sendmsg+0x268/0x2a0
[ 1417.076408] ___sys_sendmsg+0xb8/0x118
[ 1417.076427] __sys_sendmsg+0x90/0xf8
[ 1417.076445] __arm64_sys_sendmsg+0x2c/0x40
[ 1417.076465] invoke_syscall+0x50/0x120
[ 1417.076486] el0_svc_common.constprop.0+0x48/0xf0
[ 1417.076506] do_el0_svc+0x24/0x38
[ 1417.076525] el0_svc+0x30/0x100
[ 1417.076548] el0t_64_sync_handler+0x100/0x130
[ 1417.076569] el0t_64_sync+0x190/0x198
[ 1417.076589] Code: f9401e80 aa1603e2 f9403be1 5280e483 (f9400000)
Fix this, by always using the vif corresponding to the wdev on which the
Action frame Transmission request was initiated by the userspace. This way,
even if P2P vif is not available, the IOVAR is sent to firmware on AP vif
and the ANQP Query RESP Action frame is transmitted without crashing the
driver.
Move init_completion() for "send_af_done" from brcmf_p2p_create_p2pdev()
to brcmf_p2p_attach(). Because the former function would not get executed
when only hostapd is managing wlan interface, and it is not safe to do
reinit_completion() later in brcmf_p2p_tx_action_frame(), without any prior
init_completion().
And in the brcmf_p2p_tx_action_frame() function, the condition check for
P2P Presence response frame is not needed, since the wpa_supplicant is
properly sending the P2P Presense Response frame on the P2P-GO vif instead
of the P2P-Device vif.
[Cc stable](CVE-2025-40321)
In the Linux kernel, the following vulnerability has been resolved:
ASoC: topology: Check PCM and DAI name strings before use
Topology objects store several PCM and DAI names in fixed-size UAPI
arrays. Other topology parser paths validate these fields with bounded
strnlen() checks before using them as C strings, but the PCM and DAI
paths still pass some fixed-size arrays directly to strlen(),
devm_kstrdup(), DAI lookup, and diagnostic prints.
A malformed topology blob with a non-NUL-terminated PCM, DAI, or stream
capability name can therefore make the parser read past the end of the
fixed-size field.
Reject unterminated PCM and DAI name fields before consuming them as C
strings.(CVE-2026-74291)
In the Linux kernel, the following vulnerability has been resolved:
xfs: fix ilock leak on error in xfs_dq_get_next_id
xfs_dq_get_next_id() takes the quota inode ILOCK before calling
xfs_iread_extents(). If xfs_iread_extents() fails, the function returns
immediately without releasing the lock, leaking the quota inode ILOCK.
This can leave the quota inode locked and cause subsequent quota
operations to hang.
Fix this by jumping to a common unlock path on error instead of returning
directly.(CVE-2026-80534)
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: idxd: fix double free of wq, engine, and group structs
The release callbacks for wq, engine, and group devices
(idxd_conf_wq_release, idxd_conf_engine_release,
idxd_conf_group_release) each call kfree() on the enclosing struct.
The setup error paths and cleanup functions also call kfree()
explicitly after put_device(), producing a double free whenever
put_device() drops the reference count to zero and fires the release.
In the setup functions, device_initialize() is called before
device_add(), so the reference count is exactly 1 at the error sites.
put_device() unconditionally fires the release, which frees the struct;
the subsequent explicit kfree() then operates on freed memory.
For i
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
drm/dp/mst: fix buffer overflows in sideband chunk accumulation
drm_dp_sideband_append_payload() has three related bugs when processing
device-provided sideband reply data:
1. Zero-length curchunk_len underflow: msg_len is a 6-bit field taken
directly from the DP sideband header. If a device sends msg_len=0,
curchunk_len is set to zero. The condition (curchunk_idx >= curchunk_len)
is immediately true, and curchunk_len-1 wraps to 255 (u8 underflow).
drm_dp_msg_data_crc4() reads 255 bytes from chunk[48], then memcpy()
writes 255 bytes into msg[], both far out of bounds.
2. chunk[48] overflow: curchunk_len can reach 63 (6-bit field). chunk[] is
only 48 bytes. Multi-iteration payload assembly appends 16-byte blocks
until curchunk_idx reaches curchunk_len, writing up to 15 bytes past
the end of chunk[] into msg[].
3. msg[256] overflow: each chunk contributes (curchunk_len-1) bytes to
msg[]. No check ensures curlen + (curchunk_len-1) stays within msg[256],
so the memcpy can spill into adjacent struct fields.
All three are reachable from any DP MST device that can forge sideband
reply messages on a physical connection.(CVE-2026-68278)
In the Linux kernel, the following vulnerability has been resolved:
fuse: fix invalidate lock leak on open O_TRUNC DAX failure
fuse_open() takes filemap_invalidate_lock() for a DAX truncate
(dax_truncate = true) and releases it before the out_inode_unlock
label. But when fuse_dax_break_layouts() fails, the goto
out_inode_unlock skips the unlock and leaks the rwsem, so any later
fault or truncate on the file stalls on the stale lock.
fuse_dax_break_layouts() can fail with -ERESTARTSYS when a signal
interrupts the wait for busy DAX pages to drain:
open("file", O_RDWR | O_TRUNC)
└─ fuse_open()
├─ filemap_invalidate_lock() # dax_truncate
└─ fuse_dax_break_layouts()
└─ dax_break_layout()
└─ wait_page_idle() # TASK_INTERRUPTIBLE
└─ fuse_wait_dax_page() # unlock, schedule, re-lock
└─ signal → -ERESTARTSYS
goto out_inode_unlock # <- lock leaked
Fix this by moving filemap_invalidate_unlock() below the label so
that all error paths release the lock, and rename the label to
out_unlock as it now covers more than just the inode lock.(CVE-2026-80855)
In Twisted versions 25.5.0 and earlier, the wildcardToRegexp() function in twisted/mail/imap4.py improperly handles certain IMAP pattern characters by passing them directly to Python's regular expression compiler. This allows an authenticated client to craft patterns that cause catastrophic backtracking, leading to a denial of service by suspending all server input and output during the match. No fixed release is currently available.
A vulnerability in SSSD's NFS idmap plugin allows an out-of-bounds write when processing oversized cached user or group name entries. This can be triggered locally by requesting identity lookups that exceed buffer sizes, potentially causing a denial of service by crashing the identity mapping service and possibly corrupting adjacent memory. The issue affects multiple specific versions of SSSD. The CVSS score is 5.8, indicating a medium severity level.
Multiple vulnerabilities have been identified in OpenSSL affecting TLS/SSL and QUIC implementations. These include excessive memory allocation from crafted certificates causing potential denial of service, QUIC server amplification attacks due to address validation bypass, CPU exhaustion from inefficient QUIC stream reassembly, and timing side-channel leakage in elliptic-curve scalar multiplication. The vulnerabilities can lead to denial of service or private key exposure under specific conditions. A security update addressing these issues is available.
Between July and September 2026, a sophisticated campaign targeted Microsoft 365 accounts using adversary-in-the-middle attacks and token replay techniques. Attackers captured sign-in sessions via AiTM relays and replayed stolen tokens from IP addresses linked to a German hosting provider. The campaign compromised 79 organizations with 497 successful sign-ins amid over 200,000 failed attempts. Malicious actors registered rogue Entra devices, replaced victim MFA methods, and created hidden inbox rules to conceal their activities. The operation evolved through four phases, rotating IP addresses and employing scripted token and browser session replay techniques. Compromised accounts were used for business email compromise, including sending payroll-related emails to external contacts.
SiriusQT is a Windows Remote Access Trojan (RAT) distributed as Malware-as-a-Service since April 2026. It offers advanced capabilities including hidden VNC, credential theft, cryptocurrency wallet collection, clipboard monitoring, keylogging, process injection, and persistence. The malware uses custom encrypted command-and-control communication and has both native C++ and .NET loader variants. It is distributed primarily by a reseller named GhostKernel and targets victims in several European countries including the UK, Germany, France, Spain, Italy, and the Netherlands.
This content is an interview-style article profiling Corey Thuen, a hacker and CEO of Gravwell, discussing his philosophy on hacking, the concept of the 'evil bit' as an adversarial mindset, and his career path including work in cybersecurity and open source tools development. It does not describe a specific security vulnerability or threat.
This analysis covers rapid credential theft and data exfiltration attacks that occur within minutes of initial compromise, often outpacing traditional security detection and response. Attackers exploit stolen GitHub tokens, malicious AI tool installers, and MFA phishing to quickly access and exfiltrate sensitive data. Detection requires anomaly and behavior-based monitoring, while effective containment demands automated or autonomous response to minimize attacker dwell time. Manual response delays enable significant data loss. The threat highlights gaps in current identity provider detections and the need for integrated, fast-acting defense mechanisms.
In Z-Wave SDK 8.1.1 and earlier (for 700/800 series devices) and 6.85.02 and earlier (for 500 series devices), missing checks in the ZWAVE_CMD_NODES_EXIST handler can result in nodes being removed from the network. These messages must come from a device that has already joined the network.
In EmberZNet 9.1.1 and earlier, a malformed Simple_Desc_req response can result in an out-of-bounds write potentially leading to remote code execution. This response must come from a device that has already joined the network, and the attacker must wait for a Simple_Desc_req before the attack can be performed.
In EmberZNet 9.1.1 and earlier, a malformed Publish Price Matrix command can result in an out-of-bounds write potentially leading to remote code execution. These messages must come from a device that has already joined the network. Only devices supporting the Price Cluster are impacted.
A flaw has been found in subhajitkhan online-clinic-management-system up to e9ee77a8827a1446220fa07ee693dc4d9a29a578. Impacted is an unknown function of the file patappointtime.php of the component Appointment Booking. This manipulation of the argument day/time/appdate causes improper input validation. The attack can be initiated remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
