OpenWrt v19.07.9 Changelog

This changelog lists all commits done in OpenWrt since the v19.07.8 tag, grouped by subsystem. The changes are chronologically ordered from top to bottom and cover the Git repository history until the tagging of the 19.07.9 release.

See also the release notes that provide a more accessible overview of the main changes in 19.07.9.

524cbcf build: store SOURCE_DATE_EPOCH in JSON info files (+2)

b9f8668 tools/m4: update to 1.4.19 (+2,-145)

31a2d41 sdk: fix missing include directories (+6,-1)

7378c94 kernel: bump to 4.14.243 (+21,-21)
9d08255 kernel: bump to 4.14.244 (+5,-5)
9882a54 kernel: bump 4.14 to 4.14.245 (+49,-49)
93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)
662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)
5369ceb kernel: bump 4.14 to 4.14.261 (+38,-38)
974161d kernel: bump 4.14 to 4.14.262 (+9,-9)
57293f5 kernel: bump 4.14 to 4.14.264 (+84,-84)
606106f kernel: bump 4.14 to 4.14.265 (+19,-19)
3b6ce4f kernel: bump 4.14 to 4.14.266 (+2,-2)
2a3558b kernel: bump 4.14 to 4.14.267 (+25,-24)

af5c885 uboot-sunxi: Fix build with GCC-10 as host compiler (+23)
d059ce2 uboot-kirkwood: Fix build with GCC-10 as host compiler (+23)
e8cf46e uboot-layerscape: fix dtc compilation on host gcc 10 (+46)
f31bb35 uboot-mvebu: Fix build with GCC-10 as host compiler (+33)
f33dc31 uboot-tegra: Fix build with GCC-10 as host compiler (+23)
556d165 uboot-zynq: fix dtc compilation on host gcc 10 (+46)
c72ea2a uboot-lantiq: fix sha1.h header clash when system libmd installed (+172)
8fb714e uboot-lantiq: danube: fix hanging lzma kernel uncompression (+48)
f14bc5c uboot-lantiq: danube: fix hanging lzma kernel uncompression #2 (+9)

40c03b1 openssl: use --cross-compile-prefix in Configure (+2,-3)
fdea003 openssl: bump to 1.1.1l (+5,-6)
554f1b8 iproute2: m_xt.so depends on dynsyms.list (+5,-4)
b50eb70 openssl: bump to 1.1.1m (+3,-3)
e92a4e5 tcpdump: Fix CVE-2018-16301 (+102,-1)
bfa4ccc tcpdump: libpcap: Remove http://www.us.tcpdump.org mirror (+2,-4)
419b9f4 mbedtls: update to 2.16.11 (+2,-2)
1691c11 mbedtls: Update to version 2.16.12 (+2,-2)
e7596ce hostapd: Apply SAE/EAP-pwd side-channel attack update 2 (+577,-1)

a5c479a wireless-regdb: update to version 2021.04.21 (+2,-2)
b5b5262 wireless-regdb: update to version 2021.08.28 (+2,-2)

662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
5369ceb kernel: bump 4.14 to 4.14.261 (+38,-38)

5e8b962 ar71xx: mikrotik: rb91x: fix 10M ethernet link speed (+1)
662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)

1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

9d08255 kernel: bump to 4.14.244 (+5,-5)
9882a54 kernel: bump 4.14 to 4.14.245 (+49,-49)
93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)
662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)
5369ceb kernel: bump 4.14 to 4.14.261 (+38,-38)
57293f5 kernel: bump 4.14 to 4.14.264 (+84,-84)

1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)
57293f5 kernel: bump 4.14 to 4.14.264 (+84,-84)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)

7378c94 kernel: bump to 4.14.243 (+21,-21)
9882a54 kernel: bump 4.14 to 4.14.245 (+49,-49)
93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)
662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)
57293f5 kernel: bump 4.14 to 4.14.264 (+84,-84)
606106f kernel: bump 4.14 to 4.14.265 (+19,-19)
2a3558b kernel: bump 4.14 to 4.14.267 (+25,-24)

9882a54 kernel: bump 4.14 to 4.14.245 (+49,-49)
93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)
662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)
5369ceb kernel: bump 4.14 to 4.14.261 (+38,-38)

93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)
662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)
606106f kernel: bump 4.14 to 4.14.265 (+19,-19)

93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)
662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)
81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

662fe6a kernel: bump 4.14 to 4.14.254 (+53,-53)
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

93a48cb kernel: bump 4.14 to 4.14.248 (+45,-45)

81d0b4a kernel: bump 4.14 to 4.14.259 (+60,-30)

123d12e mac80211: Update to backports-4.19.207-1 (+341,-341)
cc8c1be mac80211: Update to version 4.19.221 (+55,-104)

Description: The command-line argument parser in tcpdump before 4.99.0 has a buffer overflow in tcpdump.c:read_infile(). To trigger this vulnerability the attacker needs to create a 4GB file on the local filesystem and to specify the file name as the value of the -F command-line argument of tcpdump.

Link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16301
Commits:
e92a4e5 tcpdump: Fix CVE-2018-16301 (+102,-1)

Description: u'Specifically timed and handcrafted traffic can cause internal errors in a WLAN device that lead to improper layer 2 Wi-Fi encryption with a consequent possibility of information disclosure over the air for a discrete set of traffic' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8053, IPQ4019, IPQ8064, MSM8909W, MSM8996AU, QCA9531, QCN5502, QCS405, SDX20, SM6150, SM7150

Link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3702
Commits:
123d12e mac80211: Update to backports-4.19.207-1 (+341,-341)

Description: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided.

Link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3640
Commits:
1d94f72 kernel: bump 4.14 to 4.14.258 (+99,-389)

Description: In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).

Link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3711
Commits:
fdea003 openssl: bump to 1.1.1l (+5,-6)

Description: ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).

Link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3712
Commits:
fdea003 openssl: bump to 1.1.1l (+5,-6)

Description: Mbed TLS before 3.0.1 has a double free in certain out-of-memory conditions, as demonstrated by an mbedtls_ssl_set_session() failure.

Link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44732
Commits:
1691c11 mbedtls: Update to version 2.16.12 (+2,-2)

Description: The implementations of SAE in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side channel attacks as a result of cache access patterns. NOTE: this issue exists because of an incomplete fix for CVE-2019-9494.

Link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23303
Commits:
e7596ce hostapd: Apply SAE/EAP-pwd side-channel attack update 2 (+577,-1)

Description: The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of cache access patterns. NOTE: this issue exists because of an incomplete fix for CVE-2019-9495.

Link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23304
Commits:
e7596ce hostapd: Apply SAE/EAP-pwd side-channel attack update 2 (+577,-1)