Описание
ELSA-2026-65897-0: qt5-qtbase security update (IMPORTANT)
[5.15.3-9]
- Fix CVE-2026-9499: out-of-bounds read in QTextCodec::codecForName() Resolves: RHEL-247206
Обновленные пакеты
Oracle Linux 8
Oracle Linux aarch64
qt5-qtbase
5.15.3-9.el8_10
qt5-qtbase-common
5.15.3-9.el8_10
qt5-qtbase-devel
5.15.3-9.el8_10
qt5-qtbase-examples
5.15.3-9.el8_10
qt5-qtbase-gui
5.15.3-9.el8_10
qt5-qtbase-mysql
5.15.3-9.el8_10
qt5-qtbase-odbc
5.15.3-9.el8_10
qt5-qtbase-postgresql
5.15.3-9.el8_10
qt5-qtbase-private-devel
5.15.3-9.el8_10
qt5-qtbase-static
5.15.3-9.el8_10
Oracle Linux x86_64
qt5-qtbase
5.15.3-9.el8_10
qt5-qtbase-common
5.15.3-9.el8_10
qt5-qtbase-devel
5.15.3-9.el8_10
qt5-qtbase-examples
5.15.3-9.el8_10
qt5-qtbase-gui
5.15.3-9.el8_10
qt5-qtbase-mysql
5.15.3-9.el8_10
qt5-qtbase-odbc
5.15.3-9.el8_10
qt5-qtbase-postgresql
5.15.3-9.el8_10
qt5-qtbase-private-devel
5.15.3-9.el8_10
qt5-qtbase-static
5.15.3-9.el8_10
Связанные CVE
Связанные уязвимости
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.
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.
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.
An out-of-bounds read (buffer over-read) vulnerability exists in QText ...