Openeuler
This hub aggregates every CVE we track for Openeuler, a product in the operating systems space. Use it to gauge the current risk picture and drill into individual advisories.
8
CVEs tracked
1
Critical
3
High
0
In CISA KEV
Severity distribution
MEDIUM4HIGH3CRITICAL1
Monthly trend
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2024-092026-08
Latest CVEs
The 8 most recently published vulnerabilities affecting Openeuler.
- CVE-2021-33631Kernel crash in EXT4 filesystem5.5
- CVE-2021-33630NULL-ptr-deref in network sched5.5
- CVE-2021-33640After tar_close(), libtar.c releases the memory pointed to by pointer t. After tar_close() is called in the list() function, it continues to use pointer t: free_longlink_longname(t->th_buf) . As a ...6.2
- CVE-2021-33646The th_read() function doesn’t free a variable t->th_buf.gnu_longname after allocating memory, which may cause a memory leak.7.5
- CVE-2021-33643An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnu_longlink, causing an out-of-bounds read.9.1
- CVE-2021-33645The th_read() function doesn’t free a variable t->th_buf.gnu_longlink after allocating memory, which may cause a memory leak.7.5
- CVE-2021-33644An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnu_longname, causing an out-of-bounds read.8.1
- CVE-2021-33656When setting font with malicous data by ioctl cmd PIO_FONT,kernel will write memory out of bounds.6.8
Product normalization is registry-driven with AI assist and human review. How it works