CVE-2023-52754

一、漏洞信息
 漏洞编号：[CVE-2023-52754](https://nvd.nist.gov/vuln/detail/CVE-2023-52754)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0
 CVSS V3.0分值：
 BaseScore：0.0 None
 Vector：CVSS：3.0/
 漏洞简述：
 In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver. It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor. Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.
 漏洞公开时间：2024-05-22 00:15:14
 漏洞创建时间：2024-05-21 18:58:16
 漏洞详情参考链接：
 https://nvd.nist.gov/vuln/detail/CVE-2023-52754
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/0f5068519f89d928d6c51100e4b274479123829f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/10ec5a97f8f5a772a1a42b4eb27196b447cd3aa9 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2a493a34bd6e496c55fabedd82b957193ace178f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/5e0b788fb96be36d1baf1a5c88d09c7c82a0452a |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/b083aaf5db2eeca9e362723258e5d8698f7dd84e |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52754 | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2023/CVE-2023-52754.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| suse_bugzilla | https://git.kernel.org/stable/c/0f5068519f89d928d6c51100e4b274479123829f | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| suse_bugzilla | https://git.kernel.org/stable/c/5e0b788fb96be36d1baf1a5c88d09c7c82a0452a | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| suse_bugzilla | https://git.kernel.org/stable/c/b083aaf5db2eeca9e362723258e5d8698f7dd84e | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| suse_bugzilla | https://git.kernel.org/stable/c/10ec5a97f8f5a772a1a42b4eb27196b447cd3aa9 | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| suse_bugzilla | https://git.kernel.org/stable/c/2a493a34bd6e496c55fabedd82b957193ace178f | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| suse_bugzilla | https://git.kernel.org/stable/c/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7 | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2023-52754 | https://bugzilla.suse.com/show_bug.cgi?id=1225490 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024052145-CVE-2023-52754-9725@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2282661 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2023-52754 | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://git.kernel.org/linus/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7 (6.7-rc1) | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://git.kernel.org/stable/c/0f5068519f89d928d6c51100e4b274479123829f | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://git.kernel.org/stable/c/5e0b788fb96be36d1baf1a5c88d09c7c82a0452a | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://git.kernel.org/stable/c/b083aaf5db2eeca9e362723258e5d8698f7dd84e | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://git.kernel.org/stable/c/10ec5a97f8f5a772a1a42b4eb27196b447cd3aa9 | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://git.kernel.org/stable/c/2a493a34bd6e496c55fabedd82b957193ace178f | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://git.kernel.org/stable/c/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7 | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2023-52754 | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2023-52754 | https://ubuntu.com/security/CVE-2023-52754 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2023-52754 | https://ubuntu.com/security/CVE-2023-52754 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2023-52754 |

</details>

漏洞分析指导链接：
 https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
 openBrain开源漏洞感知系统
 漏洞补丁信息：
 <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux |  | https://git.kernel.org/linus/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.
 openEuler评分：
  5.5
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP1(5.10.0):受影响
3.openEuler-22.03-LTS-SP3(5.10.0):受影响
4.openEuler-22.03-LTS-SP4(5.10.0):受影响
5.master(6.6.0):不受影响
6.openEuler-24.03-LTS(6.6.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP1(5.10.0):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.master(6.6.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-22.03-LTS-SP4(5.10.0):否

原因说明：
  1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.0):
4.openEuler-22.03-LTS-SP3(5.10.0):
5.openEuler-22.03-LTS-SP4(5.10.0):
6.openEuler-24.03-LTS(6.6.0):
7.openEuler-24.03-LTS-Next(6.6.0):

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-2324

@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen 
**issue处理注意事项:** 
**1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;**
**2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;**
**3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后cve-manager将无法正常解析填写内容.**
************************************************************************
影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响): 
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):
9.openEuler-22.03-LTS-SP4:
10.openEuler-24.03-LTS:
11.openEuler-24.03-LTS-Next:

修复是否涉及abi变化(是/否)：
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):
9.openEuler-22.03-LTS-SP4:
10.openEuler-24.03-LTS:
11.openEuler-24.03-LTS-Next:

-----------------------------------------------------------------------
issue处理具体操作请参考: 
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

<table><tr><th white-space: nowrap;>参考网址</th> <th white-space: nowrap;>关联pr</th> <th white-space: nowrap;>状态</th> <th white-space: nowrap;>补丁链接</th></tr><tr><td rowspan="1">https://nvd.nist.gov/vuln/detail/CVE-2023-52754</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7>https://git.kernel.org/stable/c/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7</a> <a href=https://git.kernel.org/stable/c/b083aaf5db2eeca9e362723258e5d8698f7dd84e>https://git.kernel.org/stable/c/b083aaf5db2eeca9e362723258e5d8698f7dd84e</a> <a href=https://git.kernel.org/stable/c/5e0b788fb96be36d1baf1a5c88d09c7c82a0452a>https://git.kernel.org/stable/c/5e0b788fb96be36d1baf1a5c88d09c7c82a0452a</a> <a href=https://git.kernel.org/stable/c/10ec5a97f8f5a772a1a42b4eb27196b447cd3aa9>https://git.kernel.org/stable/c/10ec5a97f8f5a772a1a42b4eb27196b447cd3aa9</a> <a href=https://git.kernel.org/stable/c/0f5068519f89d928d6c51100e4b274479123829f>https://git.kernel.org/stable/c/0f5068519f89d928d6c51100e4b274479123829f</a> <a href=https://git.kernel.org/stable/c/2a493a34bd6e496c55fabedd82b957193ace178f>https://git.kernel.org/stable/c/2a493a34bd6e496c55fabedd82b957193ace178f</a></td></tr><tr><td rowspan="1">https://ubuntu.com/security/CVE-2023-52754</td><td>None</td><td>None</td><td><a href=https://discourse.ubuntu.com/c/ubuntu-pro>https://discourse.ubuntu.com/c/ubuntu-pro</a></td></tr><tr><td rowspan="1">https://www.opencve.io/cve/CVE-2023-52754</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7>https://git.kernel.org/stable/c/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7</a> <a href=https://git.kernel.org/stable/c/b083aaf5db2eeca9e362723258e5d8698f7dd84e>https://git.kernel.org/stable/c/b083aaf5db2eeca9e362723258e5d8698f7dd84e</a> <a href=https://git.kernel.org/stable/c/5e0b788fb96be36d1baf1a5c88d09c7c82a0452a>https://git.kernel.org/stable/c/5e0b788fb96be36d1baf1a5c88d09c7c82a0452a</a> <a href=https://git.kernel.org/stable/c/10ec5a97f8f5a772a1a42b4eb27196b447cd3aa9>https://git.kernel.org/stable/c/10ec5a97f8f5a772a1a42b4eb27196b447cd3aa9</a> <a href=https://git.kernel.org/stable/c/0f5068519f89d928d6c51100e4b274479123829f>https://git.kernel.org/stable/c/0f5068519f89d928d6c51100e4b274479123829f</a> <a href=https://git.kernel.org/stable/c/2a493a34bd6e496c55fabedd82b957193ace178f>https://git.kernel.org/stable/c/2a493a34bd6e496c55fabedd82b957193ace178f</a></td></tr><tr><td>https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2023-52754</td><td></td><td></td><td></td></tr><tr><td rowspan="1">https://security-tracker.debian.org/tracker/CVE-2023-52754</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/linus/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7>https://git.kernel.org/linus/a1766a4fd83befa0b34d932d532e7ebb7fab1fa7</a></td></tr></table>

> 说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用[CVE补丁工具](https://gitee.com/openeuler/cve-manager/blob/master/cve-agency-manager/cve_tracking/README.md)。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

CVE-2023-52754

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

media: imon: fix access to invalid resource for the second interface

imon driver probes two USB interfaces, and at the probe of the second
interface, the driver assumes blindly that the first interface got
bound with the same imon driver.  It's usually true, but it's still
possible that the first interface is bound with another driver via a
malformed descriptor.  Then it may lead to a memory corruption, as
spotted by syzkaller; imon driver accesses the data from drvdata as
struct imon_context object although it's a completely different one
that was assigned by another driver.

This patch adds a sanity check -- whether the first interface is
really bound with the imon driver or not -- for avoiding the problem
above at the probe time.

openEuler评分:(评分和向量)
0
CVSS: 3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP1:受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS:不受影响
4.openEuler-22.03-LTS-SP1:受影响
5.openEuler-22.03-LTS-SP2:不受影响
6.openEuler-22.03-LTS-SP3:受影响
7.openEuler-22.03-LTS-SP4:不受影响
8.master(6.1.0):不受影响
9.openEuler-22.03-LTS-Next:不受影响
10.openEuler-24.03-LTS:不受影响
11.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS:否
4.openEuler-22.03-LTS-SP1:否
5.openEuler-22.03-LTS-SP2:否
6.openEuler-22.03-LTS-SP3:否
7.master(6.1.0):否
8.openEuler-22.03-LTS-Next:否
9.openEuler-24.03-LTS:否
10.openEuler-24.03-LTS-Next:否
11.openEuler-22.03-LTS-SP4:否

CVE-2023-52754

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

media: imon: fix access to invalid resource for the second interface

imon driver probes two USB interfaces, and at the probe of the second
interface, the driver assumes blindly that the first interface got
bound with the same imon driver.  It's usually true, but it's still
possible that the first interface is bound with another driver via a
malformed descriptor.  Then it may lead to a memory corruption, as
spotted by syzkaller; imon driver accesses the data from drvdata as
struct imon_context object although it's a completely different one
that was assigned by another driver.

This patch adds a sanity check -- whether the first interface is
really bound with the imon driver or not -- for avoiding the problem
above at the probe time.

openEuler评分:(评分和向量)
0
CVSS: 3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP1:受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS:不受影响
4.openEuler-22.03-LTS-SP1:受影响
5.openEuler-22.03-LTS-SP2:不受影响
6.openEuler-22.03-LTS-SP3:受影响
7.openEuler-22.03-LTS-SP4:不受影响
8.master(6.1.0):不受影响
9.openEuler-22.03-LTS-Next:不受影响
10.openEuler-24.03-LTS:不受影响
11.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS:否
4.openEuler-22.03-LTS-SP1:否
5.openEuler-22.03-LTS-SP2:否
6.openEuler-22.03-LTS-SP3:否
7.master(6.1.0):否
8.openEuler-22.03-LTS-Next:否
9.openEuler-24.03-LTS:否
10.openEuler-24.03-LTS-Next:否
11.openEuler-22.03-LTS-SP4:否

CVE-2023-52754

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

media: imon: fix access to invalid resource for the second interface

imon driver probes two USB interfaces, and at the probe of the second
interface, the driver assumes blindly that the first interface got
bound with the same imon driver.  It's usually true, but it's still
possible that the first interface is bound with another driver via a
malformed descriptor.  Then it may lead to a memory corruption, as
spotted by syzkaller; imon driver accesses the data from drvdata as
struct imon_context object although it's a completely different one
that was assigned by another driver.

This patch adds a sanity check -- whether the first interface is
really bound with the imon driver or not -- for avoiding the problem
above at the probe time.

openEuler评分:(评分和向量)
0
CVSS: 3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP1:受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS:不受影响
4.openEuler-22.03-LTS-SP1:受影响
5.openEuler-22.03-LTS-SP2:不受影响
6.openEuler-22.03-LTS-SP3:受影响
7.openEuler-22.03-LTS-SP4:不受影响
8.master(6.1.0):不受影响
9.openEuler-22.03-LTS-Next:不受影响
10.openEuler-24.03-LTS:不受影响
11.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS:否
4.openEuler-22.03-LTS-SP1:否
5.openEuler-22.03-LTS-SP2:否
6.openEuler-22.03-LTS-SP3:否
7.master(6.1.0):否
8.openEuler-22.03-LTS-Next:否
9.openEuler-24.03-LTS:否
10.openEuler-24.03-LTS-Next:否
11.openEuler-22.03-LTS-SP4:否

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It's usually true, but it's stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it's a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.|
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|  In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time. |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|    In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.  |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@ci-robot 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|    In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.  |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|    In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.  |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|      In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.   |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|        In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.    |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|          In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.     |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|            In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.      |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|              In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.       |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@chenyi211 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|              In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.       |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|                In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.        |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|                  In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.         |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|                    In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.          |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|                      In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.           |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|                        In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.            |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

@guo-mengqi 请完成以下操作:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|                          In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It s usually true, but it s stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it s a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.             |
|待分析|2.openEulerScore|2.openEulerScore=> 没有填写或正确填写(0-10)|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性,待分析内容请填写完整,否则将无法关闭当前issue.**

CVE-2023-52754

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

media: imon: fix access to invalid resource for the second interface

imon driver probes two USB interfaces, and at the probe of the second
interface, the driver assumes blindly that the first interface got
bound with the same imon driver.  It's usually true, but it's still
possible that the first interface is bound with another driver via a
malformed descriptor.  Then it may lead to a memory corruption, as
spotted by syzkaller; imon driver accesses the data from drvdata as
struct imon_context object although it's a completely different one
that was assigned by another driver.

This patch adds a sanity check -- whether the first interface is
really bound with the imon driver or not -- for avoiding the problem
above at the probe time.

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:受影响
2.openEuler-22.03-LTS-SP1:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:受影响
7.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否

===========================================================

CVE-2023-52754

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

media: imon: fix access to invalid resource for the second interface

imon driver probes two USB interfaces, and at the probe of the second
interface, the driver assumes blindly that the first interface got
bound with the same imon driver.  It's usually true, but it's still
possible that the first interface is bound with another driver via a
malformed descriptor.  Then it may lead to a memory corruption, as
spotted by syzkaller; imon driver accesses the data from drvdata as
struct imon_context object although it's a completely different one
that was assigned by another driver.

This patch adds a sanity check -- whether the first interface is
really bound with the imon driver or not -- for avoiding the problem
above at the probe time.

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:受影响
2.openEuler-22.03-LTS-SP1:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:受影响
7.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否

===========================================================

@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It's usually true, but it's stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it's a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.|
|已分析|2.openEulerScore|5.5|
|已分析|3.openEulerVector|AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,master:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.**

CVE-2023-52754

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

media: imon: fix access to invalid resource for the second interface

imon driver probes two USB interfaces, and at the probe of the second
interface, the driver assumes blindly that the first interface got
bound with the same imon driver.  It's usually true, but it's still
possible that the first interface is bound with another driver via a
malformed descriptor.  Then it may lead to a memory corruption, as
spotted by syzkaller; imon driver accesses the data from drvdata as
struct imon_context object although it's a completely different one
that was assigned by another driver.

This patch adds a sanity check -- whether the first interface is
really bound with the imon driver or not -- for avoiding the problem
above at the probe time.

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:受影响
2.openEuler-22.03-LTS-SP1:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:不受影响
7.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否

@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:media: imon: fix access to invalid resource for the second interfaceimon driver probes two USB interfaces, and at the probe of the secondinterface, the driver assumes blindly that the first interface gotbound with the same imon driver.  It's usually true, but it's stillpossible that the first interface is bound with another driver via amalformed descriptor.  Then it may lead to a memory corruption, asspotted by syzkaller; imon driver accesses the data from drvdata asstruct imon_context object although it's a completely different onethat was assigned by another driver.This patch adds a sanity check -- whether the first interface isreally bound with the imon driver or not -- for avoiding the problemabove at the probe time.|
|已分析|2.openEulerScore|5.5|
|已分析|3.openEulerVector|AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,master:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|