media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt()
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH 1/1 media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt()
The bounds checking in avc_ca_pmt() is not strict enough. It should be checking "read_pos + 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.
I also added checks for the "write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me.
The other problem is that "length" can be invalid. It comes from "data_length" in fdtv_ca_pmt().
---
This hardware isn't super common so there is no embargo. Resending through normal lists.
Oh, another thing is the data_length calculation in fdtv_ca_pmt() seems very suspicous. Reading more than 4 bytes in the loop will lead to shift wrapping.
drivers/media/firewire/firedtv-avc.c | 14 +++++++++++--- drivers/media/firewire/firedtv-ci.c | 2 ++ 2 files changed, 13 insertions(+), 3 deletions(-)
drivers/media/firewire/firedtv-avc.c +11 -3
@@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) read_pos += program_info_length; write_pos += program_info_length; } -while (read_pos < length) { +while (read_pos +4 < length) { +if (write_pos +4 >=sizeof (c->operand) -4 ) { + ret = -EINVAL ; + goto out; + } c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++];
@@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) c->operand[write_pos++] = es_info_length >>8 ; c->operand[write_pos++] = es_info_length &0xff ;if (es_info_length >0 ) { +if (read_pos >= length) { + ret = -EINVAL ; + goto out; + } pmt_cmd_id = msg[read_pos++];if (pmt_cmd_id !=1 && pmt_cmd_id !=4 )dev_err (fdtv->device,"invalid pmt_cmd_id %d at stream level\n" , pmt_cmd_id); -if (es_info_length >sizeof (c->operand) -4 - - write_pos) { +if (es_info_length >sizeof (c->operand) -4 - write_pos || + es_info_length > length - read_pos) { ret = -EINVAL ; goto out; }
drivers/media/firewire/firedtv-ci.c +2 -0
@@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg) }else { data_length = msg->msg[3 ]; } +if (data_length >sizeof (msg->msg) -4 ) +return -EINVAL ;return avc_ca_pmt (fdtv, &msg->msg[data_pos], data_length); }
Signature · 1 line
2.30.2
Quoted 10 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me.
Quoted 6 lines
The other problem is that "length" can be invalid. It comes from "
data_length" infdtv_ca_pmt().Reported-by Luo Likang <[email protected]>Signed-off-by Dan Carpenter <[email protected]>
Thanks for the report and the fix!
As a quick note on alternative mitigations, it seems that CONFIG_UBSAN_BOUNDS would have caught this at runtime too. (i.e. c->operand[]'s size is known at build time, so out of bounds indexing should be detected.)
-Kees
Quoted 65 lines
---
This hardware isn't super common so there is no embargo. Resending through normal lists.Oh, another thing is the
data_lengthcalculation infdtv_ca_pmt()seems very suspicous. Reading more than 4 bytes in the loop will lead to shift wrapping.drivers/media/firewire/firedtv-avc.c | 14 +++++++++++--- drivers/media/firewire/firedtv-ci.c | 2 ++ 2 files changed, 13 insertions(+), 3 deletions(-)drivers/media/firewire/firedtv-avc.c +11
-3@@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) read_pos += program_info_length; write_pos += program_info_length; } -while (read_pos < length) { +while (read_pos +4 < length) { +if (write_pos +4 >=sizeof (c->operand) -4 ) { + ret = -EINVAL ; + goto out; + } c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++];@@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) c->operand[write_pos++] = es_info_length >>8 ; c->operand[write_pos++] = es_info_length &0xff ;if (es_info_length >0 ) { +if (read_pos >= length) { + ret = -EINVAL ; + goto out; + } pmt_cmd_id = msg[read_pos++];if (pmt_cmd_id !=1 && pmt_cmd_id !=4 )dev_err (fdtv->device,"invalid pmt_cmd_id %d at stream level\n" , pmt_cmd_id); -if (es_info_length >sizeof (c->operand) -4 - - write_pos) { +if (es_info_length >sizeof (c->operand) -4 - write_pos || + es_info_length > length - read_pos) { ret = -EINVAL ; goto out; }drivers/media/firewire/firedtv-ci.c +2
-0@@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg) }else { data_length = msg->msg[3 ]; } +if (data_length >sizeof (msg->msg) -4 ) +return -EINVAL ;return avc_ca_pmt (fdtv, &msg->msg[data_pos], data_length); }Signature · 1 line
2.30.2
Signature · 1 line
Kees Cook
PATCH v2 1/1 media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt()
In reply to Dan CarpenterThe bounds checking in avc_ca_pmt() is not strict enough. It should be checking "read_pos + 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.
I also added checks for the "write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me. The check on write_pos is:
if (write_pos + 4 >= sizeof(c->operand) - 4) {The first "+ 4" is because we're writing 5 bytes and the last " - 4" is to leave space for the CRC.
The other problem is that "length" can be invalid. It comes from "data_length" in fdtv_ca_pmt().
---
v2: Change the limit in fdtv_ca_pmt() from "sizeof(msg->msg) - 4" to "sizeof(msg->msg) - data_pos".
Oh, another thing is the data_length calculation in fdtv_ca_pmt() seems very suspicous. Reading more than 4 bytes in the loop will lead to shift wrapping.
drivers/media/firewire/firedtv-avc.c | 14 +++++++++++--- drivers/media/firewire/firedtv-ci.c | 2 ++ 2 files changed, 13 insertions(+), 3 deletions(-)
drivers/media/firewire/firedtv-avc.c +11 -3
@@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) read_pos += program_info_length; write_pos += program_info_length; } -while (read_pos < length) { +while (read_pos +4 < length) { +if (write_pos +4 >=sizeof (c->operand) -4 ) { + ret = -EINVAL ; + goto out; + } c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++];
@@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) c->operand[write_pos++] = es_info_length >>8 ; c->operand[write_pos++] = es_info_length &0xff ;if (es_info_length >0 ) { +if (read_pos >= length) { + ret = -EINVAL ; + goto out; + } pmt_cmd_id = msg[read_pos++];if (pmt_cmd_id !=1 && pmt_cmd_id !=4 )dev_err (fdtv->device,"invalid pmt_cmd_id %d at stream level\n" , pmt_cmd_id); -if (es_info_length >sizeof (c->operand) -4 - - write_pos) { +if (es_info_length >sizeof (c->operand) -4 - write_pos || + es_info_length > length - read_pos) { ret = -EINVAL ; goto out; }
drivers/media/firewire/firedtv-ci.c +2 -0
@@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg) }else { data_length = msg->msg[3 ]; } +if (data_length >sizeof (msg->msg) - data_pos) +return -EINVAL ;return avc_ca_pmt (fdtv, &msg->msg[data_pos], data_length); }
Signature · 1 line
2.30.2
Quoted 15 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me. The check onwrite_posis:if (write_pos + 4 >= sizeof(c->operand) - 4) {The first "+ 4" is because we're writing 5 bytes and the last " - 4" is to leave space for the CRC.
Quoted 6 lines
The other problem is that "length" can be invalid. It comes from "
data_length" infdtv_ca_pmt().Reported-by Luo Likang <[email protected]>Signed-off-by Dan Carpenter <[email protected]>
I do not see this fix in 5.14-rc1. Has it been solved another way in the end, please?
Best Regards,
Petr
This was marked as superseded in patchwork. What are we going to apply instead?
regards,
dan carpenter
Quoted 80 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me.The other problem is that "length" can be invalid. It comes from "
data_length" infdtv_ca_pmt().Reported-by Luo Likang <[email protected]>Signed-off-by Dan Carpenter <[email protected]>---
This hardware isn't super common so there is no embargo. Resending through normal lists.Oh, another thing is the
data_lengthcalculation infdtv_ca_pmt()seems very suspicous. Reading more than 4 bytes in the loop will lead to shift wrapping.drivers/media/firewire/firedtv-avc.c | 14 +++++++++++--- drivers/media/firewire/firedtv-ci.c | 2 ++ 2 files changed, 13 insertions(+), 3 deletions(-)drivers/media/firewire/firedtv-avc.c +11
-3@@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) read_pos += program_info_length; write_pos += program_info_length; } -while (read_pos < length) { +while (read_pos +4 < length) { +if (write_pos +4 >=sizeof (c->operand) -4 ) { + ret = -EINVAL ; + goto out; + } c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++];@@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) c->operand[write_pos++] = es_info_length >>8 ; c->operand[write_pos++] = es_info_length &0xff ;if (es_info_length >0 ) { +if (read_pos >= length) { + ret = -EINVAL ; + goto out; + } pmt_cmd_id = msg[read_pos++];if (pmt_cmd_id !=1 && pmt_cmd_id !=4 )dev_err (fdtv->device,"invalid pmt_cmd_id %d at stream level\n" , pmt_cmd_id); -if (es_info_length >sizeof (c->operand) -4 - - write_pos) { +if (es_info_length >sizeof (c->operand) -4 - write_pos || + es_info_length > length - read_pos) { ret = -EINVAL ; goto out; }drivers/media/firewire/firedtv-ci.c +2
-0@@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg) }else { data_length = msg->msg[3 ]; } +if (data_length >sizeof (msg->msg) -4 ) +return -EINVAL ;return avc_ca_pmt (fdtv, &msg->msg[data_pos], data_length); }Signature · 1 line
2.30.2
Quoted 81 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me.The other problem is that "length" can be invalid. It comes from "
data_length" infdtv_ca_pmt().Reported-by Luo Likang <[email protected]>Signed-off-by Dan Carpenter <[email protected]>---
This hardware isn't super common so there is no embargo. Resending through normal lists.Oh, another thing is the
data_lengthcalculation infdtv_ca_pmt()seems very suspicous. Reading more than 4 bytes in the loop will lead to shift wrapping.drivers/media/firewire/firedtv-avc.c | 14 +++++++++++--- drivers/media/firewire/firedtv-ci.c | 2 ++ 2 files changed, 13 insertions(+), 3 deletions(-)drivers/media/firewire/firedtv-avc.c +11
-3@@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) read_pos += program_info_length; write_pos += program_info_length; } -while (read_pos < length) { +while (read_pos +4 < length) { +if (write_pos +4 >=sizeof (c->operand) -4 ) { + ret = -EINVAL ; + goto out; + } c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++];@@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) c->operand[write_pos++] = es_info_length >>8 ; c->operand[write_pos++] = es_info_length &0xff ;if (es_info_length >0 ) { +if (read_pos >= length) { + ret = -EINVAL ; + goto out; + } pmt_cmd_id = msg[read_pos++];if (pmt_cmd_id !=1 && pmt_cmd_id !=4 )dev_err (fdtv->device,"invalid pmt_cmd_id %d at stream level\n" , pmt_cmd_id); -if (es_info_length >sizeof (c->operand) -4 - - write_pos) { +if (es_info_length >sizeof (c->operand) -4 - write_pos || + es_info_length > length - read_pos) { ret = -EINVAL ; goto out; }drivers/media/firewire/firedtv-ci.c +2
-0@@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg) }else { data_length = msg->msg[3 ]; } +if (data_length >sizeof (msg->msg) -4 ) +return -EINVAL ;return avc_ca_pmt (fdtv, &msg->msg[data_pos], data_length); }Signature · 1 line
2.30.2
This patch seems to have gotten lost. Any change of it getting applied?
thanks,
greg k-h
Hi,
Quoted 77 lines · Greg KH
Quoted 76 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me.The other problem is that "length" can be invalid. It comes from "
data_length" infdtv_ca_pmt().Reported-by Luo Likang <[email protected]>Signed-off-by Dan Carpenter <[email protected]>---
This hardware isn't super common so there is no embargo. Resending through normal lists.Oh, another thing is the
data_lengthcalculation infdtv_ca_pmt()seems very suspicous. Reading more than 4 bytes in the loop will lead to shift wrapping.drivers/media/firewire/firedtv-avc.c | 14 +++++++++++--- drivers/media/firewire/firedtv-ci.c | 2 ++ 2 files changed, 13 insertions(+), 3 deletions(-)drivers/media/firewire/firedtv-avc.c +11
-3@@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) read_pos += program_info_length; write_pos += program_info_length; } -while (read_pos < length) { +while (read_pos +4 < length) { +if (write_pos +4 >=sizeof (c->operand) -4 ) { + ret = -EINVAL ; + goto out; + } c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++];@@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) c->operand[write_pos++] = es_info_length >>8 ; c->operand[write_pos++] = es_info_length &0xff ;if (es_info_length >0 ) { +if (read_pos >= length) { + ret = -EINVAL ; + goto out; + } pmt_cmd_id = msg[read_pos++];if (pmt_cmd_id !=1 && pmt_cmd_id !=4 )dev_err (fdtv->device,"invalid pmt_cmd_id %d at stream level\n" , pmt_cmd_id); -if (es_info_length >sizeof (c->operand) -4 - - write_pos) { +if (es_info_length >sizeof (c->operand) -4 - write_pos || + es_info_length > length - read_pos) { ret = -EINVAL ; goto out; }drivers/media/firewire/firedtv-ci.c +2
-0@@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg) }else { data_length = msg->msg[3 ]; } +if (data_length >sizeof (msg->msg) -4 ) +return -EINVAL ;
Quoted 7 lines
Quoted 5 lines
drivers/media/firewire/firedtv-ci.c +0
-0return avc_ca_pmt (fdtv, &msg->msg[data_pos], data_length); }Signature · 1 line
2.30.2This patch seems to have gotten lost. Any change of it getting applied?
As far I can see there was then a version 2 of the patch, but that one got list somewhere. Friendly ping on this thread :)
Regards,
Salvatore
PATCH RESEND v2 1/1 media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt()
The bounds checking in avc_ca_pmt() is not strict enough. It should be checking "read_pos + 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.
I also added checks for the "write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me. The check on write_pos is:
if (write_pos + 4 >= sizeof(c->operand) - 4) {The first "+ 4" is because we're writing 5 bytes and the last " - 4" is to leave space for the CRC.
The other problem is that "length" can be invalid. It comes from "data_length" in fdtv_ca_pmt(). Added a check in fdtv_ca_pmt() to prevent that.
---
RESEND: this patch got lost somehow.
v2: Change the limit in fdtv_ca_pmt() from "sizeof(msg->msg) - 4" to "sizeof(msg->msg) - data_pos".
Oh, another thing is the data_length calculation in fdtv_ca_pmt() seems very suspicous. Reading more than 4 bytes in the loop will lead to shift wrapping.
drivers/media/firewire/firedtv-avc.c | 14 +++++++++++--- drivers/media/firewire/firedtv-ci.c | 2 ++ 2 files changed, 13 insertions(+), 3 deletions(-)
drivers/media/firewire/firedtv-avc.c +11 -3
@@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) read_pos += program_info_length; write_pos += program_info_length; } -while (read_pos < length) { +while (read_pos +4 < length) { +if (write_pos +4 >=sizeof (c->operand) -4 ) { + ret = -EINVAL ; + goto out; + } c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++];
@@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) c->operand[write_pos++] = es_info_length >>8 ; c->operand[write_pos++] = es_info_length &0xff ;if (es_info_length >0 ) { +if (read_pos >= length) { + ret = -EINVAL ; + goto out; + } pmt_cmd_id = msg[read_pos++];if (pmt_cmd_id !=1 && pmt_cmd_id !=4 )dev_err (fdtv->device,"invalid pmt_cmd_id %d at stream level\n" , pmt_cmd_id); -if (es_info_length >sizeof (c->operand) -4 - - write_pos) { +if (es_info_length >sizeof (c->operand) -4 - write_pos || + es_info_length > length - read_pos) { ret = -EINVAL ; goto out; }
drivers/media/firewire/firedtv-ci.c +2 -0
@@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg) }else { data_length = msg->msg[3 ]; } +if (data_length >sizeof (msg->msg) - data_pos) +return -EINVAL ;return avc_ca_pmt (fdtv, &msg->msg[data_pos], data_length); }
Signature · 1 line
2.30.2
Quoted 19 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me. The check onwrite_posis:if (write_pos + 4 >= sizeof(c->operand) - 4) {The first "+ 4" is because we're writing 5 bytes and the last " - 4" is to leave space for the CRC.
The other problem is that "length" can be invalid. It comes from "
data_length" infdtv_ca_pmt(). Added a check infdtv_ca_pmt()to prevent that.
Quoted 6 lines
Reported-by Luo Likang <[email protected]>Signed-off-by Dan Carpenter <[email protected]>---
RESEND: this patch got lost somehow.
What the heck? Someone on patchwork just marked this patch as obsolete again!!!
Mauro can you figure out who's doing that and what's going on? The first time it was marked as obsolete then I asked about it twice, Greg asked about it, and Salvatore Bonaccorso asked about it. But all we get are anonymous notifications from patchwork. It's a bit frustrating.
regards,
dan carpenter
Hi,
[linux-distros list dropped as not anymore relevant for embargo]
Quoted 27 lines · Dan Carpenter
Quoted 19 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me. The check onwrite_posis:if (write_pos + 4 >= sizeof(c->operand) - 4) {The first "+ 4" is because we're writing 5 bytes and the last " - 4" is to leave space for the CRC.
The other problem is that "length" can be invalid. It comes from "
data_length" infdtv_ca_pmt(). Added a check infdtv_ca_pmt()to prevent that.Quoted 6 lines
Reported-by Luo Likang <[email protected]>Signed-off-by Dan Carpenter <[email protected]>---
RESEND: this patch got lost somehow.
Quoted 7 lines
What the heck? Someone on patchwork just marked this patch as obsolete again!!!
Mauro can you figure out who's doing that and what's going on? The first time it was marked as obsolete then I asked about it twice, Greg asked about it, and Salvatore Bonaccorso asked about it. But all we get are anonymous notifications from patchwork. It's a bit frustrating.
Someone knows what is going on here, i.e. what is the problem?
Regards,
Salvatore
Quoted 11 lines · Salvatore Bonaccorso
Quoted 9 lines · Dan Carpenter
Quoted 8 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough.
They may be in sync at a fixed offset, but the buffer length of the read ("int length") is not in sync with the buffer length for the write ("sizeof(c->operand)").
So I do think the write pos limit checking is actually necessary and needed.
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
RESEND: this patch got lost somehow.
What the heck? Someone on patchwork just marked this patch as obsolete again!!!
Can we please make sure patchwork has some logging so that that kind of thing shows _who_ did this?
Quoted 1 line
Someone knows what is going on here, i.e. what is the problem?
Dan, can you just send that fix to me directly, with the fixed commit message (see above), and we can close this.
That still leaves the "who closes things on patchwork" question, but that's something I can't do anything about.
Linus
Quoted 19 lines · Linus Torvalds
Quoted 11 lines · Salvatore Bonaccorso
Quoted 9 lines · Dan Carpenter
Quoted 8 lines · Dan Carpenter
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough.They may be in sync at a fixed offset, but the buffer length of the read ("int length") is not in sync with the buffer length for the write ("
sizeof(c->operand)").So I do think the write pos limit checking is actually necessary and needed.
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
RESEND: this patch got lost somehow.
What the heck? Someone on patchwork just marked this patch as obsolete again!!!
Can we please make sure patchwork has some logging so that that kind of thing shows _who_ did this?
It's not easily visible in the web UI, but patchwork does log that sort of info.
The v2 RESEND is:
https://patchwork.linuxtv.org/project/linux-media/patch/20210816072721.GA10534@kili/
In the top right is the patch id (76352), you can then get the list of events for that patch at:
https://patchwork.linuxtv.org/api/events/?patch=76352
Which shows that hverkuil changed it to obsolete on 2021-09-01T10:16:43.
Presumably because they picked up the non-resend version, which was marked as under-review around the same time:
https://patchwork.linuxtv.org/api/events/?patch=74849
And then also visible on the above page, it was marked as accepted by mchehab on 2021-09-03T13:06:16.
But I don't see the patch in linux-next, or in linux-media.git, so I'm not sure where it's been accepted to?
cheers
Mauro Carvalho Chehab
Acked-byEm Sun, 12 Sep 2021 11:26:10 -0700
Linus Torvalds <[email protected]> escreveu:
Quoted 19 lines · Salvatore Bonaccorso
Quoted 11 lines · Dan Carpenter
Quoted 9 lines · Dan Carpenter
Quoted 8 lines
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough.They may be in sync at a fixed offset, but the buffer length of the read ("int length") is not in sync with the buffer length for the write ("
sizeof(c->operand)").So I do think the write pos limit checking is actually necessary and needed.
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
RESEND: this patch got lost somehow.
What the heck? Someone on patchwork just marked this patch as obsolete again!!!
Can we please make sure patchwork has some logging so that that kind of thing shows _who_ did this?
I've been wanting a feature like that on patchwork for years. Basically, when there's more then a single person capable of accessing a patchwork instance, there's no way to log who changed the status, nor to control who can delegate a patch to someone else or not.
At least for me, touching patchwork is very hard, as the the entire login logic, as well as the database model itself, is abstracted by Django. So, I can't simply change a SQL insert clause there to add something else to their logs nor to change the sent email that it is pushed when a patch status changed.
I ended adding an internal log to indicate when I do some changes on my patchwork instance via script a couple of years ago.
Quoted 4 lines
Quoted 1 line
Someone knows what is going on here, i.e. what is the problem?
Dan, can you just send that fix to me directly, with the fixed commit message (see above), and we can close this.
Feel free to add my:
Quoted 3 lines
That still leaves the "who closes things on patchwork" question, but that's something I can't do anything about.
I'll double-check my scripts in order to identify if this came from my side, and if so, fix them.
Thanks,
Mauro
Hi Dan,
Quoted 44 lines · Mauro Carvalho Chehab
Em Sun, 12 Sep 2021 11:26:10 -0700
Linus Torvalds <[email protected]> escreveu:Quoted 19 lines · Salvatore Bonaccorso
Quoted 11 lines · Dan Carpenter
Quoted 9 lines · Dan Carpenter
Quoted 8 lines
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough.They may be in sync at a fixed offset, but the buffer length of the read ("int length") is not in sync with the buffer length for the write ("
sizeof(c->operand)").So I do think the write pos limit checking is actually necessary and needed.
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
RESEND: this patch got lost somehow.
What the heck? Someone on patchwork just marked this patch as obsolete again!!!
Can we please make sure patchwork has some logging so that that kind of thing shows _who_ did this?
I've been wanting a feature like that on patchwork for years. Basically, when there's more then a single person capable of accessing a patchwork instance, there's no way to log who changed the status, nor to control who can delegate a patch to someone else or not.
At least for me, touching patchwork is very hard, as the the entire login logic, as well as the database model itself, is abstracted by Django. So, I can't simply change a SQL insert clause there to add something else to their logs nor to change the sent email that it is pushed when a patch status changed.
I ended adding an internal log to indicate when I do some changes on my patchwork instance via script a couple of years ago.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
Someone knows what is going on here, i.e. what is the problem?
Dan, can you just send that fix to me directly, with the fixed commit message (see above), and we can close this.
Feel free to add my:
I'm sorry for prodding again, I guess I'm becoming a bit annoying :-/
Dan, could you sent the patch with the above to Linus directly so it can show up in at least 5.15-rc3? I guess it's now to late for 5.15-rc2.
Regards,
Salvatore
Hi,
Quoted 54 lines · Salvatore Bonaccorso
Hi Dan,
Quoted 51 lines · Mauro Carvalho Chehab
Em Sun, 12 Sep 2021 11:26:10 -0700
Linus Torvalds <[email protected]> escreveu:Quoted 19 lines · Salvatore Bonaccorso
Quoted 11 lines · Dan Carpenter
Quoted 9 lines · Dan Carpenter
Quoted 8 lines
The bounds checking in
avc_ca_pmt()is not strict enough. It should be checking "read_pos+ 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.I also added checks for the "
write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough.They may be in sync at a fixed offset, but the buffer length of the read ("int length") is not in sync with the buffer length for the write ("
sizeof(c->operand)").So I do think the write pos limit checking is actually necessary and needed.
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
RESEND: this patch got lost somehow.
What the heck? Someone on patchwork just marked this patch as obsolete again!!!
Can we please make sure patchwork has some logging so that that kind of thing shows _who_ did this?
I've been wanting a feature like that on patchwork for years. Basically, when there's more then a single person capable of accessing a patchwork instance, there's no way to log who changed the status, nor to control who can delegate a patch to someone else or not.
At least for me, touching patchwork is very hard, as the the entire login logic, as well as the database model itself, is abstracted by Django. So, I can't simply change a SQL insert clause there to add something else to their logs nor to change the sent email that it is pushed when a patch status changed.
I ended adding an internal log to indicate when I do some changes on my patchwork instance via script a couple of years ago.
Quoted 4 lines
Quoted 1 line
Someone knows what is going on here, i.e. what is the problem?
Dan, can you just send that fix to me directly, with the fixed commit message (see above), and we can close this.
Feel free to add my:
Quoted 7 lines
Quoted 1 line
I'm sorry for prodding again, I guess I'm becoming a bit annoying :-/
Dan, could you sent the patch with the above to Linus directly so it can show up in at least 5.15-rc3? I guess it's now to late for 5.15-rc2.
It looks this is still not yet applied up to 5.15-rc5, if I'm not mistaken.
Regards,
Salvatore
PATCH 1/1 media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt()
The bounds checking in avc_ca_pmt() is not strict enough. It should be checking "read_pos + 4" because it's reading 5 bytes. If the "es_info_length" is non-zero then it reads a 6th byte so there needs to be an additional check for that.
I also added checks for the "write_pos". I don't think these are required because "read_pos" and "write_pos" are tied together so checking one ought to be enough. But they make the code easier to understand for me. The check on write_pos is:
if (write_pos + 4 >= sizeof(c->operand) - 4) {The first "+ 4" is because we're writing 5 bytes and the last " - 4" is to leave space for the CRC.
The other problem is that "length" can be invalid. It comes from "data_length" in fdtv_ca_pmt().
---
Cherry picked from linux-next.
drivers/media/firewire/firedtv-avc.c | 14 +++++++++++--- drivers/media/firewire/firedtv-ci.c | 2 ++ 2 files changed, 13 insertions(+), 3 deletions(-)
drivers/media/firewire/firedtv-avc.c +11 -3
@@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) read_pos += program_info_length; write_pos += program_info_length; } -while (read_pos < length) { +while (read_pos +4 < length) { +if (write_pos +4 >=sizeof (c->operand) -4 ) { + ret = -EINVAL ; + goto out; + } c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++]; c->operand[write_pos++] = msg[read_pos++];
@@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length) c->operand[write_pos++] = es_info_length >>8 ; c->operand[write_pos++] = es_info_length &0xff ;if (es_info_length >0 ) { +if (read_pos >= length) { + ret = -EINVAL ; + goto out; + } pmt_cmd_id = msg[read_pos++];if (pmt_cmd_id !=1 && pmt_cmd_id !=4 )dev_err (fdtv->device,"invalid pmt_cmd_id %d at stream level\n" , pmt_cmd_id); -if (es_info_length >sizeof (c->operand) -4 - - write_pos) { +if (es_info_length >sizeof (c->operand) -4 - write_pos || + es_info_length > length - read_pos) { ret = -EINVAL ; goto out; }
drivers/media/firewire/firedtv-ci.c +2 -0
@@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg) }else { data_length = msg->msg[3 ]; } +if (data_length >sizeof (msg->msg) - data_pos) +return -EINVAL ;return avc_ca_pmt (fdtv, &msg->msg[data_pos], data_length); }
Signature · 1 line
2.20.1