24590 matches found
hfsplus: fix KMSAN uninit-value issue in __hfsplus_ext_cache_extent()
...
scsi: sg: Do not sleep in atomic context
...
net: openvswitch: remove never-working support for setting nsh fields
...
mptcp: fix race condition in mptcp_schedule_work()
...
nios2: ensure that memblock.current_limit is set when setting pfn limits
...
sctp: avoid NULL dereference when chunk data buffer is missing
...
mptcp: fix a race in mptcp_pm_del_add_timer()
...
nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl()
...
Improper validation of <img> tag size in Text component parser
...
Improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509
...
Input: cros_ec_keyb - fix an invalid memory access
...
drm/msm: Fix pgtable prealloc error path
...
s390/ctcm: Fix double-kfree
...
gfs2: Fix unlikely race in gdlm_put_lock
...
Input: imx_sc_key - fix memory corruption on unload
...
erofs: Fix detection of atomic context
...
wifi: mac80211_hwsim: Fix possible NULL dereference
...
mtd: core: fix possible resource leak in init_mtd()
...
drm/amdkfd: Fix double release compute pasid
...
XSS in Bootstrap button component
...
In Eclipse Paho Go MQTT v3.1 library (paho.mqtt.golang) versions <=1.5.0 UTF-8 encoded strings, passed into the library, may be incorrectly encoded if their length exceeds 65535 bytes. This may lead to unexpected content in packets sent to the server (for example, part of an MQTT topic may leak into the message body in a PUBLISH packet). The issue arises because the length of the data passed in was converted from an int64/int32 (depending upon CPU) to an int16 without checks for overflows. The int16 length was then written, followed by the data (e.g. topic). This meant that when the data (e.g. topic) was over 65535 bytes then the amount of data written exceeds what the length field indicates. This could lead to a corrupt packet, or mean that the excess data leaks into another field (e.g. topic leaks into message body).
...
PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV
...
fuse: fix livelock in synchronous file put from fuseblk workers
...
pidfs: validate extensible ioctls
...
mm/damon/vaddr: do not repeat pte_offset_map_lock() until success
...
xfrm: delete x->tunnel as we delete x
...
Out-of-memory when loading Plist
...
Excessive read buffering DoS in http.client
...
Untrusted search path in auth_query connection in PgBouncer
...
LIBPNG has an out-of-bounds read in png_image_read_composite
...
KissFFT Integer Overflow Heap Buffer Overflow via kiss_fft_alloc
...
Vim for Windows Uncontrolled Search Path Element Remote Code Execution Vulnerability
...
cacheinfo: Fix shared_cpu_map to handle shared caches at different levels
...
drm/amdgpu: install stub fence into potential unused fence pointers
...
btrfs: set_page_extent_mapped after read_folio in btrfs_cont_expand
...
xsk: check IFF_UP earlier in Tx path
...
bpf: Fix memleak due to fentry attach failure
...
rxrpc: Make it so that a waiting process can be aborted
...
orangefs: Fix kmemleak in orangefs_sysfs_init()
...
Excessive resource consumption when printing error string for host certificate validation in crypto/x509
...
Chromium: CVE-2025-13640 Inappropriate implementation in Passwords
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13639 Inappropriate implementation in WebRTC
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13638 Use after free in Media Stream
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13637 Inappropriate implementation in Downloads
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13636 Inappropriate implementation in Split View
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13635 Inappropriate implementation in Downloads
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13720 Bad cast in Loader
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13721 Race in v8
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13634 Inappropriate implementation in Downloads
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2025-13633 Use after free in Digital Credentials
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...