Hazley Samsudin

**Name of the Vulnerable Software and Affected Versions** The product name cannot be determined (affected versions not specified) **Description** An integer overflow occurs in the `dsp mmap single()` function when validating requested mappings by summing a user-supplied offset and length against the buffer size. A large offset and length can wrap around, bypassing the check. Subsequently, the offset is narrowed from 64 to 32 bits during conversion to a buffer address, creating a mapping that extends beyond the audio buffer into unrelated kernel memory. Because `/dev/dsp` device nodes are world-accessible by default, an unprivileged local user can read and write kernel memory. This can lead to privilege escalation, full system control, or a Denial of Service (DoS) by crashing the kernel. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Notepad++ version 8.9.3 **Description** A format string injection exists in the Find Results panel handler. This occurs when the application processes a maliciously crafted `nativeLang.xml` language pack file. An attacker can distribute a poisoned language pack through community channels; when a user performs search operations, the application triggers format string interpretation. This can lead to access violations, denial of service, and the potential leakage of stack or register contents (information disclosure). **Recommendations** As a temporary workaround, avoid installing or using untrusted `nativeLang.xml` language packs from community channels.

**Name of the Vulnerable Software and Affected Versions** Notepad++ versions prior to 8.9.4 **Description** A string injection issue exists in the FindInFiles search function due to flaws in the formatting string processing mechanism. Successful exploitation could allow an attacker to obtain sensitive memory address information or cause the application to crash (denial of service) by using a specially crafted file. This risk is particularly relevant for users utilizing custom `nativeLang.xml` localization files. **Recommendations** Update to version 8.9.4 or later. Avoid using untrusted configuration or localization files.