337 lines
26 KiB
JSON
337 lines
26 KiB
JSON
{
|
||
"Definition": [
|
||
{
|
||
"ID": "oval:org.altlinux.errata:def:20221722",
|
||
"Version": "oval:org.altlinux.errata:def:20221722",
|
||
"Class": "patch",
|
||
"Metadata": {
|
||
"Title": "ALT-PU-2022-1722: package `kernel-image-std-debug` update to version 5.4.189-alt1",
|
||
"AffectedList": [
|
||
{
|
||
"Family": "unix",
|
||
"Platforms": [
|
||
"ALT Linux branch p9"
|
||
],
|
||
"Products": [
|
||
"ALT Server",
|
||
"ALT Virtualization Server",
|
||
"ALT Workstation",
|
||
"ALT Workstation K",
|
||
"ALT Education",
|
||
"Simply Linux",
|
||
"Starterkit"
|
||
]
|
||
}
|
||
],
|
||
"References": [
|
||
{
|
||
"RefID": "ALT-PU-2022-1722",
|
||
"RefURL": "https://errata.altlinux.org/ALT-PU-2022-1722",
|
||
"Source": "ALTPU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-05007",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-05007",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-05008",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-05008",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-05009",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-05009",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-05189",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-05189",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-05400",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-05400",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-05409",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-05409",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-05410",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-05410",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-23036",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-23036",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-23037",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-23037",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-23038",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-23038",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-23039",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-23039",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-23040",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-23040",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-23041",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-23041",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-23042",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-23042",
|
||
"Source": "CVE"
|
||
}
|
||
],
|
||
"Description": "This update upgrades kernel-image-std-debug to version 5.4.189-alt1. \nSecurity Fix(es):\n\n * BDU:2022-05007: Уязвимость компонента netfront гипервизора Xen, позволяющая нарушителю вызвать отказ в обслуживании\n\n * BDU:2022-05008: Уязвимость компонентов blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront и pvcalls гипервизора Xen, позволяющая нарушителю вызвать отказ в обслуживании\n\n * BDU:2022-05009: Уязвимость компонента xenbus гипервизора Xen, позволяющая нарушителю вызвать отказ в обслуживании\n\n * BDU:2022-05189: Уязвимость драйвера gntalloc гипервизора Xen, позволяющая нарушителю вызвать отказ в обслуживании\n\n * BDU:2022-05400: Уязвимость утилиты гипервизора Xen, вызванная ошибками синхронизации при использовании общего ресурса, позволяющая нарушителю вызвать отказ в обслуживании\n\n * BDU:2022-05409: Уязвимость драйвера scsifront команды PV гипервизора Xen, позволяющая нарушителю вызвать отказ в обслуживании\n\n * BDU:2022-05410: Уязвимость драйвера blkfront команды PV гипервизора Xen, позволяющая нарушителю вызвать отказ в обслуживании\n\n * CVE-2022-23036: Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042\n\n * CVE-2022-23037: Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042\n\n * CVE-2022-23038: Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042\n\n * CVE-2022-23039: Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042\n\n * CVE-2022-23040: Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042\n\n * CVE-2022-23041: Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042\n\n * CVE-2022-23042: Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042",
|
||
"Advisory": {
|
||
"From": "errata.altlinux.org",
|
||
"Severity": "High",
|
||
"Rights": "Copyright 2024 BaseALT Ltd.",
|
||
"Issued": {
|
||
"Date": "2022-04-19"
|
||
},
|
||
"Updated": {
|
||
"Date": "2022-04-19"
|
||
},
|
||
"bdu": [
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:S/C:C/I:C/A:C",
|
||
"Cvss3": "AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-05007",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "BDU:2022-05007"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:S/C:C/I:C/A:C",
|
||
"Cvss3": "AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-05008",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "BDU:2022-05008"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:S/C:C/I:C/A:C",
|
||
"Cvss3": "AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-05009",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "BDU:2022-05009"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:S/C:C/I:C/A:C",
|
||
"Cvss3": "AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-05189",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "BDU:2022-05189"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:S/C:C/I:C/A:C",
|
||
"Cvss3": "AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362, CWE-617",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-05400",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "BDU:2022-05400"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:L/Au:S/C:C/I:C/A:C",
|
||
"Cvss3": "AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-05409",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "BDU:2022-05409"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:S/C:C/I:C/A:C",
|
||
"Cvss3": "AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-05410",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "BDU:2022-05410"
|
||
}
|
||
],
|
||
"Cves": [
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:N/C:P/I:P/A:P",
|
||
"Cvss3": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-23036",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "CVE-2022-23036"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:N/C:P/I:P/A:P",
|
||
"Cvss3": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-23037",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "CVE-2022-23037"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:N/C:P/I:P/A:P",
|
||
"Cvss3": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-23038",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "CVE-2022-23038"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:N/C:P/I:P/A:P",
|
||
"Cvss3": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-23039",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "CVE-2022-23039"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:N/C:P/I:P/A:P",
|
||
"Cvss3": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-23040",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "CVE-2022-23040"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:N/C:P/I:P/A:P",
|
||
"Cvss3": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-23041",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "CVE-2022-23041"
|
||
},
|
||
{
|
||
"Cvss": "AV:L/AC:M/Au:N/C:P/I:P/A:P",
|
||
"Cvss3": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"Cwe": "CWE-362",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-23042",
|
||
"Impact": "High",
|
||
"Public": "20220310",
|
||
"CveID": "CVE-2022-23042"
|
||
}
|
||
],
|
||
"AffectedCpeList": {
|
||
"Cpe": [
|
||
"cpe:/o:alt:kworkstation:9",
|
||
"cpe:/o:alt:workstation:9",
|
||
"cpe:/o:alt:server:9",
|
||
"cpe:/o:alt:server-v:9",
|
||
"cpe:/o:alt:education:9",
|
||
"cpe:/o:alt:slinux:9",
|
||
"cpe:/o:alt:starterkit:p9",
|
||
"cpe:/o:alt:kworkstation:9.1",
|
||
"cpe:/o:alt:workstation:9.1",
|
||
"cpe:/o:alt:server:9.1",
|
||
"cpe:/o:alt:server-v:9.1",
|
||
"cpe:/o:alt:education:9.1",
|
||
"cpe:/o:alt:slinux:9.1",
|
||
"cpe:/o:alt:starterkit:9.1",
|
||
"cpe:/o:alt:kworkstation:9.2",
|
||
"cpe:/o:alt:workstation:9.2",
|
||
"cpe:/o:alt:server:9.2",
|
||
"cpe:/o:alt:server-v:9.2",
|
||
"cpe:/o:alt:education:9.2",
|
||
"cpe:/o:alt:slinux:9.2",
|
||
"cpe:/o:alt:starterkit:9.2"
|
||
]
|
||
}
|
||
}
|
||
},
|
||
"Criteria": {
|
||
"Operator": "AND",
|
||
"Criterions": [
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:1001",
|
||
"Comment": "ALT Linux must be installed"
|
||
}
|
||
],
|
||
"Criterias": [
|
||
{
|
||
"Operator": "OR",
|
||
"Criterions": [
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722001",
|
||
"Comment": "kernel-headers-modules-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722002",
|
||
"Comment": "kernel-headers-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722003",
|
||
"Comment": "kernel-image-domU-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722004",
|
||
"Comment": "kernel-image-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722005",
|
||
"Comment": "kernel-modules-drm-ancient-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722006",
|
||
"Comment": "kernel-modules-drm-nouveau-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722007",
|
||
"Comment": "kernel-modules-drm-radeon-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722008",
|
||
"Comment": "kernel-modules-drm-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722009",
|
||
"Comment": "kernel-modules-ide-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722010",
|
||
"Comment": "kernel-modules-midgard-be-m1000-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722011",
|
||
"Comment": "kernel-modules-staging-std-debug is earlier than 2:5.4.189-alt1"
|
||
},
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221722012",
|
||
"Comment": "kernel-modules-v4l-std-debug is earlier than 2:5.4.189-alt1"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|
||
}
|
||
]
|
||
} |