当前Pull Request已关闭, 关闭人@openeuler-ci-bot
Welcome To openEuler Community
Hey @protkhn , thanks for your contribution to the community.
Bot Usage Manual
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands.
Contact Guide
If you have any questions, please contact the SIG: Application ,
and any of the maintainers: @kaitiandu, @small_leek, @zhuchunyi ,
and any of the committers: @caodongxia, @starlet-dx, @wk333 .
当前仓库存在以下 保护分支 ：
| Protected Branch | Version | Release |
|---|---|---|
| master | 4.6.8 | 1 |
| openEuler-24.03-LTS-Next | 4.6.8 | 1 |
| openEuler-26.09-DevStation | 4.6.8 | 1 |
| openEuler-22.03-LTS-SP4 | 4.4.18 | 1 |
| openEuler-24.03-LTS-SP3 | 4.4.18 | 1 |
| openEuler-24.03-LTS-SP1 | 4.4.18 | 1 |
| openEuler-24.03-LTS-SP4 | 4.4.18 | 1 |
| openEuler-26.09 | 4.6.7 | 1 |
| openEuler-20.03-LTS-SP4 | 3.6.14 | 14 |
| openEuler1.0-base | 2.6.2 | 6 |
| openEuler1.0 | 2.6.2 | 4 |
评论 /sync <branch1> <branch2> ... 可将当前 PR 修改同步到其它分支（创建同步 PR）：
a) 如果当前 PR 是 Open 状态，同步操作将延迟到 PR 被合并时执行
b) 如果当前 PR 已经 Merged，将立即执行同步操作
注意：
- /sync 命令可以指定同步到多个分支，仅最后一个 /sync 命令生效
- 如果创建的同步 PR 不正确，可通过向同步 PR 的源分支提交轻量级 PR 完善，或使用 /close 命令关闭
门禁正在运行， 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决，可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/wireshark/62/console
aarch64架构构建及构建后检查：multiarch/src-openeuler/aarch64/wireshark/62/console
x86_64架构构建及构建后检查：multiarch/src-openeuler/x86-64/wireshark/62/console
| Check Name | Build Result | 详情 | Build Details | |
|---|---|---|---|---|
| check_binary_file | ✅SUCCESS | #62 | ||
| check_lfsconfig | :ballot_box_with_check:EXCLUDE | |||
| check_package_yaml_file | ✅SUCCESS | |||
| check_repo_in_maintain | ✅SUCCESS | |||
| check_consistency | ✅SUCCESS | |||
| check_spec_file | ✅SUCCESS | |||
| x86_64 | check_build | ✅SUCCESS | #62 | |
| check_install | ✅SUCCESS | |||
| check_license | ✅SUCCESS | |||
| aarch64 | check_build | ✅SUCCESS | #62 | |
| check_install | ✅SUCCESS | |||
| check_license | ✅SUCCESS | |||
如下为接口变更检查结果，目标分支为openEuler-20.03-LTS-SP4，请PR提交者check差异信息
| Arch Name | Check Items | Rpm Name | Check Result | Build Details |
|---|---|---|---|---|
| compare_package(x86_64) | add_rpms | ✅SUCCESS | #62 | |
| delete_rpms | ✅SUCCESS | |||
| rpm_abi | ✅SUCCESS | |||
| rpm_cmd | ✅SUCCESS | |||
| rpm_files | ✅SUCCESS | |||
| rpm_header | wireshark-devel | ❌FAILED | ||
| rpm_lib | ✅SUCCESS | |||
| rpm_provides | ✅SUCCESS | |||
| rpm_requires | ✅SUCCESS | |||
| rpm_symbol | ✅SUCCESS | |||
| compare_package(aarch64) | add_rpms | ✅SUCCESS | #62 | |
| delete_rpms | ✅SUCCESS | |||
| rpm_abi | ✅SUCCESS | |||
| rpm_cmd | ✅SUCCESS | |||
| rpm_files | ✅SUCCESS | |||
| rpm_header | wireshark-devel | ❌FAILED | ||
| rpm_lib | ✅SUCCESS | |||
| rpm_provides | ✅SUCCESS | |||
| rpm_requires | ✅SUCCESS | |||
| rpm_symbol | ✅SUCCESS |
当前PR是否有AI参与
[ ] 否
[x] Yes
参考：openEuler社区
https://www.openeuler.org/zh/community/aigc/PR功能描述 / 为什么需要这个合入
wiretap: busmaster: Do not exit the program on a malformed file
修复 CVE-2026-76926（wnpa-sec-2026-70）。BUSMASTER 日志解析器在未结束的 header/time 语句中遇到换行时，会走 Flex 的 YY_FATAL_ERROR 致命错误路径，直接调用 exit(2) 终止进程，而不是按 wiretap 的正常错误流程返回解析错误。攻击者可通过诱导用户打开构造的 BUSMASTER 日志文件，使 Wireshark/TShark 或嵌入 libwiretap 的长期运行进程异常退出，造成拒绝服务。上游改为设置 yyextra->err = WTAP_ERR_BAD_FILE 并 yyterminate()，交由正常的 wiretap 错误处理流程上报。
上游来源：https://github.com/wireshark/wireshark/commit/8e984f1f8360d90c5250c1a77b8754f3ce64890b
修复类型：安全修复
回合说明：基于 wireshark 3.6.14 版本回合上游补丁。上游仅在 4.4.18 / 4.6.8 发布修复，3.6 分支无对应回合版本，故从 master 修复 commit 回合。3.6.14 中 busmaster_state_t 已包含 err / err_info 字段，busmaster_priv.h 已引入 wiretap/wtap.h（提供 WTAP_ERR_BAD_FILE），run_busmaster_parser 的错误传递路径与上游 4.4 完全一致，补丁可干净合入且语义正确。已从零解压 tarball 依次打入全部 29 个 patch 验证通过。ABI：安全，仅修改 wiretap/busmaster_scanner.l 这一 flex 扫描器内部实现，不涉及公开头文件与导出符号签名变更。
该PR关联的issue
fixes #220
希望检视人员了解
代码由AI辅助编写，已人工逐行核对逻辑、校验功能正确性，确保与预期一致。