928 matches found
CVE-2026-63838
In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of componentdais componentdaisRSNDMAXCOMPONENT is initially zero-initialized and later populated in rsnddaiofnode. However, the existing boundary check: if i = RSNDMAXCOMPONENT does...
CVE-2026-63908 Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
In the Linux kernel, the following vulnerability has been resolved: Input: atmelmxtts - fix boundary check in mxtpreparecfgmem When a configuration file provides an object size that is larger than the driver's known mxtobjsizeobject, the driver intends to discard the extra bytes. The loop iterate...
EUVD-2026-45681
In the Linux kernel, the following vulnerability has been resolved: Input: atmelmxtts - fix boundary check in mxtpreparecfgmem When a configuration file provides an object size that is larger than the driver's known mxtobjsizeobject, the driver intends to discard the extra bytes. The loop iterate...
CVE-2026-63908
The CVE-2026-63908 entry concerns the Linux kernel driver for atmel_mxt_ts. A configuration file could supply an object size larger than the driver’s known mxt_obj_size(object); the code intended to discard extra bytes but used a faulty loop bound, checking for i > mxt_obj_size(object). Since ...
CVE-2026-63908 Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
In the Linux kernel, the following vulnerability has been resolved: Input: atmelmxtts - fix boundary check in mxtpreparecfgmem When a configuration file provides an object size that is larger than the driver's known mxtobjsizeobject, the driver intends to discard the extra bytes. The loop iterate...
CVE-2026-63908
In the Linux kernel, the following vulnerability has been resolved: Input: atmelmxtts - fix boundary check in mxtpreparecfgmem When a configuration file provides an object size that is larger than the driver's known mxtobjsizeobject, the driver intends to discard the extra bytes. The loop iterate...
EUVD-2026-45522
In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of componentdais componentdaisRSNDMAXCOMPONENT is initially zero-initialized and later populated in rsnddaiofnode. However, the existing boundary check: if i = RSNDMAXCOMPONENT does...
CVE-2026-63838
The CVE-2026-63838 entry concerns the Linux kernel ASoC rsnd subsystem. It fixes a potential out-of-bounds access in rsnd_dai_of_node() caused by a boundary check (i >= RSND_MAX_COMPONENT) not guaranteeing component_dais[RSND_MAX_COMPONENT] remains zero, so a loop could read past the end of th...
CVE-2026-63838 ASoC: rsnd: Fix potential out-of-bounds access of component_dais[]
In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of componentdais componentdaisRSNDMAXCOMPONENT is initially zero-initialized and later populated in rsnddaiofnode. However, the existing boundary check: if i = RSNDMAXCOMPONENT does...
CVE-2026-63838 ASoC: rsnd: Fix potential out-of-bounds access of component_dais[]
In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of componentdais componentdaisRSNDMAXCOMPONENT is initially zero-initialized and later populated in rsnddaiofnode. However, the existing boundary check: if i = RSNDMAXCOMPONENT does...
CVE-2026-63838
In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of componentdais componentdaisRSNDMAXCOMPONENT is initially zero-initialized and later populated in rsnddaiofnode. However, the existing boundary check: if i = RSNDMAXCOMPONENT does...
PT-2026-61225
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A boundary check error exists in the atmel mxt ts driver within the mxt prepare cfg mem function. When a configuration file specifies an object size larger than the driver's known mxt ob...
PT-2026-61155
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An out-of-bounds access issue exists in the ASoC rsnd component. The component dais array is zero-initialized and populated via the rsnd dai of node function. Because the boundary check ...
PYSEC-2026-2426 compliance-trestle Profile Import has an Arbitrary File Read via trestle:// URI and Relative Path Traversal
Summary The compliance-trestle library's profile import mechanism resolves trestle:// URIs and relative file paths by joining them with trestleroot and calling .resolve, but performs no boundary check to ensure the resolved path stays within the trestle workspace. An attacker can craft a maliciou...
PYSEC-2026-2999 Regression in pymdownx.snippets reintroduces sibling-prefix path traversal bypass despite restrict_base_path
Summary pymdownx.snippets has a regression of the CVE-2023-32309 / GHSA-jh85-wwv9-24hv fix. With restrictbasepath: True the default, the current filename.startswithbase containment check does not enforce a directory boundary. As a result, a markdown snippet directive can read files from sibling...
CVE-2026-57257
During the PRC parsing stage, there is a lack of boundary verification for the PRC entity index, which leads to an out-of-bounds read of the entity array. As a result, the application crashes...
CVE-2026-57257 Security vulnerability in Foxit PDF Editor/Reader — PRC 3D BRep Renderer Heap OOB Read
During the PRC parsing stage, there is a lack of boundary verification for the PRC entity index, which leads to an out-of-bounds read of the entity array. As a result, the application crashes...
PT-2026-56356
Name of the Vulnerable Software and Affected Versions Foxit PDF Editor/Reader affected versions not specified Description During the PRC parsing stage, a lack of boundary verification for the PRC entity index allows an out-of-bounds read of the entity array, causing the application to crash...
BIT-PYTHON-MIN-2026-3298 Out-of-bounds write in Windows asyncio.ProacterEventLoop.sock_recvfrom_into() when using nbytes
The method "sockrecvfrominto" of "asyncio.ProacterEventLoop" Windows only was missing a boundary check for the data buffer when using nbytes parameter. This allowed for an out-of-bounds buffer write if data was larger than the buffer size. Non-Windows platforms are not affected...
BIT-PYTHON-2026-3298 Out-of-bounds write in Windows asyncio.ProacterEventLoop.sock_recvfrom_into() when using nbytes
The method "sockrecvfrominto" of "asyncio.ProacterEventLoop" Windows only was missing a boundary check for the data buffer when using nbytes parameter. This allowed for an out-of-bounds buffer write if data was larger than the buffer size. Non-Windows platforms are not affected...