Source: qt6-5compat
Version: 6.10.2-3
Severity: important
Tags: security upstream
X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>
Control: clone -1 -2
Control: reassign -2 src:qtbase-opensource-src 5.15.19+dfsg-3
Control: retitle -2 qtbase-opensource-src: CVE-2026-9499

Hi,

The following vulnerability was published for Qt5Compat module from
Qt.

CVE-2026-9499[0]:
| An out-of-bounds read (buffer over-read) vulnerability exists in
| QTextCodec::codecForName() in Qt. When the function is called with a
| QByteArray that is not NUL-terminated (for example, one created with
| QByteArray::fromRawData()), the codec-name matching routine reads
| past the end of the supplied buffer. In most cases this results in
| an incorrect text codec being selected; in the worst case, if the
| over-read reaches unmapped memory, the process crashes (denial of
| service). The over-read is bounded by the length of the longest
| codec-name candidate, and the out-of-bounds bytes are only compared
| internally against Qt's fixed list of codec names, so no data is
| disclosed to an attacker. Applications that do not pass non-NUL-
| terminated QByteArrays to QTextCodec::codecForName() are not
| exposed. The affected code resides in the Qt5Compat module from Qt
| 6.0.0 onward, and in Qt Core (qtbase) in Qt 4.x and Qt 5.x.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-9499
    https://www.cve.org/CVERecord?id=CVE-2026-9499

Please adjust the affected versions in the BTS as needed.



-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 7.1.3+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Reply via email to